feat(navigation-logo): adds component tokens

[anveshmekala]

Related Issue: #7180

Summary

Adds the following tokens in calcite-navigation-logo component

--calcite-navigation-logo-background-color: Specifies the background color of the component.
--calcite-navigation-logo-border-color: Specifies the border color of the component.
--calcite-navigation-logo-description-text-color: Specifies text color of description of component.
--calcite-navigation-logo-heading-text-color: Specifies the text color of heading of component.
--calcite-navigation-logo-text-color: Specifies the text color of the component.

[alisonailea]

Per Adam's comment. I don't think we need stateful tokens here. I've shown three ways to get to the tokens we need here. I'd vote 1. or 2. but it's up to you.

[anveshmekala]

I don't think we need stateful tokens here.

This part i am bit confused. Initially had them and later removed them and added back. The refactor doc says tokens should be added for appropriate states. I can see the reasoning for adding them since hover and active are appropriate states for navigation-logo component. On the other hand, user can simply set the state on component selector and change the token variable if required.

Are we adding state tokens for components which are inaccessible to the user (inside shadowDOM) or components which can used as sub-components for other components?

[alisonailea]

🎉 Looks great! Thanks