feat!: Introduce brand color palettes and rename color tokens

[VincentSmedinga]

Describe the pull request

Thank you for contributing to the project!
Please use this template to help us handle your PR smoothly.

What

• This introduces tints and shades of all our colours.
• All colour tokens have been renamed, e.g. from ams.color.primary-blue to ams.brand.color.blue.60.
• Interactive components that are invalid now become dark red on hover.
• The colour ‘green’ has been renamed to ‘lime’, ‘dark green’ to ‘green’, ‘blue’ to ‘azure’, and ‘primary-blue’ to ‘blue’, and the other ‘primary’ colours have lost that prefix as well.
• As little as possible usages of colour have been changed – only everything ‘disabled’ now uses neutral.60 consistently.

Why

• To define a darker hover color and a lighter background colour for every colour in the palette.
• To introduce a consistent naming scheme for all colours.

How

• Generated tints and shades through Supa Palette for Figma
• Replaced ams.color.* with ams.brand.color.*
• Updated all token references in components
• Updated the Color Palette component and colour docs

Upcoming pull requests will update the colour names in props, introduce common tokens, add more consistency, prefix other brand tokens, etc.

[dlnr]

I would like to suggest that we merge this not in develop but in branch where we can merge multiple colour palette changes. Because this changes a lot of common (component) tokens that will probably be changed again when we implement semantic colour tokens.