[OUDS] Css: drop deprecated Boosted variables and change deprecated comments

[julien-deramond]

Related issues

Listed in #2589

Description

This PR handles the "deprecate" comments in JavaScript and Sass files.

The rules are the following:

• If the deprecation comment comes from Bootstrap, keep it and include the word "Bootstrap" in it
• If the deprecation comment comes from Boosted and relies on Bootstrap values, change it to OUDS Web, and keep the Boosted previous values for Boosted projects migrating to OUDS Web
• If the deprecation comment comes from Boosted only, the corresponding variable(s) can be removed from the framework

All removed Sass variables are listed in the Boosted migration guide.

Types of change

• Refactoring (non-breaking change)

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	29c5986
🔍 Latest deploy log	https://app.netlify.com/sites/boosted/deploys/669f5c6310ab32000874716c
😎 Deploy Preview	https://deploy-preview-2638--boosted.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[louismaximepiton]

I think it lacks a bit of consistency between all the deprecating messages. I think it would be great to have the rules for those messages stored in the description and not only the rules for search & replace. For instance, we have deprecated in Bootstrap * but can we use it in OUDS since we have deprecation messages like deprecated in OUDS? Maybe a clear message like: Not to be used in OUDS because it is deprecated in Bootstrap v* or something similar everywhere would be safer. I also think that we could write the rules and keep the rewording when we will reintroduce things little by little.

One small change is needed and we could launch the PR imo.