Add spright custom colored icons for calendar work item types

[vivinkrishna-ni]

Pull Request

🤨 Rationale

Nimble icons currently do not have a way to change colors based on the requirements, especially when used within Nimble table components. While Nimble provides color override mechanisms, these cannot be applied when icons are used in table cells through the mapping-icon component.

This is a application-specific requirement, so utilizing the Spright to register the icons for different types of work items.

👩‍💻 Implementation

1. Extends IconSvg for Nimble table compatibility
2. Imports SVG data from nimble-tokens to reuse existing assets
3. Applies custom styles with specific calendar event color design tokens
4. Registers with spright prefix via FAST DesignSystem
5. Exports class and tag constant for type-safe usage
6. Create 5 custom colored event icons:
   1. calendar-calibration
   2. calendar-maintenance
   3. calendar-reservation
   4. calendar-test-plan
   5. calendar-transport-order

🧪 Testing

Verified from the storybook build.

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.

[github-actions]

Dependency Review

The following issues were found:

• ❌ 1 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.

View full job summary

[rajsite]

For symmetry with nimble can you call this file all-icons.ts instead of index.ts?

[rajsite]

After the other rename can just do:

Suggested change

	import './icons/calendar-calibration';
	import './icons/calendar-maintenance';
	import './icons/calendar-reservation';
	import './icons/calendar-test-plan';
	import './icons/calendar-transport-order';
	import './icons/all-icons';

[rajsite]

Doens't look like any nimble-components changes are in this PR, can remove this change file

[rajsite]

Are you planning to make spright-angular directives for the icons? Could be in a follow-up or in this PR

[jattasNI]

I'm sure you're aware but in case you forgot: you'll need to do framework integration work for these components since you can't rely on the code generation approach we use for core Nimble icons. If you only need Angular it's ok to stop there, but Blazor and React integration are appreciated. This can happen in a follow up PR.