feat(skin): Solve button primary contrast issues

[aweell]

Warning

Do not merge this PR until spacing alignment project is merged in web, in order to avoid more screenshot changes

Pull Request Description: feat(skin): Solve button primary contrast issues

This pull request addresses and resolves contrast issues with primary buttons in our UI. The motivation behind this change is to enhance accessibility and ensure that our button text is easily readable against its background, adhering to WCAG (Web Content Accessibility Guidelines) standards.

Key Changes:

1. New Contrast Pairs: Added new contrast pairs for negative button states, ensuring that text on negative buttons meets the minimum contrast ratio of 4.5.
2. Color Adjustments: Adjusted several button background colors from beyondBlue30 to beyondBlue10 and beyondBlue15 for various button states (hovered, pressed) to improve contrast and visibility.

Benefits:

• Improved Accessibility: By enhancing color contrast, we make our buttons more legible for users with visual impairments, ensuring a more inclusive user experience.
• Consistency: This update maintains consistent styling across our button variants while adhering to design principles and accessibility standards.

In summary, these changes will significantly improve the usability and accessibility of our application, making it more user-friendly for all.

[aweell]

We should review badge in dark, is failing against textPrimaryNegative:

[contrast-fail] dark.textPrimaryNegative vs dark.badge
Suggestion: grey20 (#F3F3F5, 4.59)

I may not change the text token value, since matches the rest of other texts (default, brand...) so the option here is to update badge value to a darker tone.

This would require to create a new palette entry o2new70 (#A73939) that will have 4.5 against grey30

[aweell]

We should review badge in dark, is failing against textPrimaryNegative:

[contrast-fail] dark.textPrimaryNegative vs dark.badge Suggestion: grey20 (#F3F3F5, 4.59)

I may not change the text token value, since matches the rest of other texts (default, brand...) so the option here is to update badge value to a darker tone.

This would require to create a new palette entry o2new70 (#A73939) that will have 4.5 against grey30

We should review badge in dark, is failing against textPrimaryNegative:

[contrast-fail] dark.textPrimaryNegative vs dark.badge Suggestion: grey20 (#F3F3F5, 4.59)

I may not change the text token value, since matches the rest of other texts (default, brand...) so the option here is to update badge value to a darker tone.

This would require to create a new palette entry o2new70 (#A73939) that will have 4.5 against grey30

Will be solved in #2584