Review opinionated theme for all components

[raquelarrojo]

Describe the bug
Default theme is not correct in several components. Also, some components do not have default theme and it should be included.

To Reproduce
Default theme can be checked for all components using ux config.

Expected behaviour
Default theme should be corrected for all the components, following the guidelines. Also, some of the new components should have default theme too.

[aidamag]

Fixes to be done:

• [Quick nav] document default theme inputs in website #1381 . We should add them in the themes page.
  Also, token selectedFontColor is not used in the component. We should remove it from HalstackContext.
  

• [Select] fix default theme inputs in the documentation #1382 . We should add the default theme input optionFontColor for the token listOptionFontColor and remove listOptionFontColor from the theme input fontColor.

• [Slider] wrong token totalLineColor when using default theme #1383 . When using default theme, totalLineColor is getting two opacities at the same time:
  

First one (value 57) is from HalstackContext:

And the second one (value 61) is from the own component:

We should keep the first value (57) so totalLineColor can be changed when changing theme input baseColor.

• [Switch] Theme input fontColor is not defined in the documentation #1384 . We should add it in the themes page with the token labelFontColor.

• Table: I would add an example in the Theme Builder and UX Config of the Resultset Table component.

• [Wizard] Typo in HalstackContext and wrong documentation. #1385 . In the documentation, move the token selectedStepBorderColor to the list of the theme input baseColor.
  Besides, theme input selectedFontColor is not working because there is a typo in HalstackContext:
  

SelectedStepFontColor should not be using fontColor but selectedFontColor:
wizardTokens.selectedStepFontColor = theme?.wizard?.selectedFontColor ?? wizardTokens.selectedStepFontColor;

[aidamag]

Components without default theme inputs:

• Alert: old component, it didn't have default theme inputs from the beginning.
• App Layout: new component, maybe default theme input for the hamburguer.
• Bleed: new component, no point of having default theme inputs as it is a layout.
• Box: old component, it didn't have default theme inputs from the beginning.
• Bulleted List: new component, maybe we could add default theme input for fontColor.
• Card: old component, it didn't have default theme inputs from the beginning.
• Dialog: old component, it didn't have default theme inputs from the beginning.
• Flex: new component, no point of having default theme inputs as it is a layout.
• Heading: old component, it didn't have default theme inputs from the beginning, maybe we could add one for fontColor.
• Inset: new component, no point of having default theme inputs as it is a layout.
• Link: old component. Font color can be changed with the prop inheritColor. However, we could add a default theme input accentColor like in the links of the quick nav component for the hover and active status.
• Nav Tabs: new component. Maybe as in the tabs, to add baseColor.
• Paragraph: new component, no point of having default theme inputs.
• Textarea: old component, as with the text input component, we could add fontColor.
• Quick Nav: new component, explained in the comment above.
• Tag: old component. Maybe fontColor as default theme input.
• Typography: new component, no point of having default theme inputs.