Issue number: internal

What is the new behavior?

• Removed old tokens stored on foundations folder. Now the jsons with the tokens come from the new dependency: https://github.com/OutSystems/outsystems-design-tokens.
• The tokens from UX Team completely changed the structure and in some cases the values. Everything was replaced on the project to use the new tokens.
• Snapshots updated and differences reviewed with UX Team. A fix was done on the testing css, to make sure the correct Inter font-family was actually used. This resulted in some differences on the text for some componentes, that had snapshots with the native fonts.
• Removed generation of scss file on tokens script, that contained the :root selector with the custom CSS properties, as they were not used on the Ionic context.
• Removed generation of html file with tokens preview, as there wasn't a great value on this (we have storybook on other contexts) and it allowed to reduce a lot of code and complexity from the tokens script.
• The token command was adapted to use the command available from the https://github.com/OutSystems/outsystems-design-tokens package, using the --config prop, where we pass the path to our Ionic token script, where we generate the needed scss variables and utility-classes (by default the tokens repo tries to be as agnostic as possible, and only generates the css variables, without the prefix and added details we need on the Ionic side).
• Removed the token command from the npm run build, as it unnecessarily added time on that command to run. Besides, it should not be common that we need to run this command in the future.
• Updated reference to latest version of Style Dictionary 4.1.3. Version 4 comes with a lot of improvements, but also breaking-changes, so it was needed to adapt the tokens script. The code on the script is also now cleaner.
• Changed prefix from ionic to ion. The term ionic was used initially, to help differentiate from the old ios/md stuff, but I feel with the current scss architecture, that is no longer needed, and we can use the same prefix across themes.

This requires to run npm install again.

Does this introduce a breaking change?

• Yes
• No