docs: add design callouts in all the documentation when incompatibility with ODS

[isabellechanclou]

Related issues

Closes #1199
Closes #1118
Closes #1117

Description

Everywhere needed in Boosted Docs, a callout message has been added.

Motivation & Context

Callout messages added to warn Boosted users that such component or component variant should not be used because incompatible with the orange design system specifications.

Types of change

• New feature (non-breaking change which adds functionality)

Live previews

• https://deploy-preview-1614--boosted.netlify.app/

Checklist

• I have read the contributing guidelines
• My code follows the code style of the project (using npm run lint)
• My change introduces changes to the documentation
• My change introduces changes to the migration guide
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	4fcd51d
🔍 Latest deploy log	https://app.netlify.com/sites/boosted/deploys/659bcea1f6fbd000083c8162
😎 Deploy Preview	https://deploy-preview-1614--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]

Here are some global comments, feel free to debate about these.

I'd rather use should not instead of can not almost everywhere in the callouts.
The way they are implemented yet make me feel that a callout is for the entire subpart.
Wondering if we should redirect to a usable Boosted variant on each callout ?
Maybe be more descriptive on some components.
Maybe we should on some examples explain why we shouldn't use this particular example but the concepts behind are still usable ?
We don't have specs for placeholders but is it fine to use them ?
Be brave for the migration guide change !

[hannahiss]

Reviewed up to customize-colors included

[louismaximepiton]

Still some comments inside the PR to take into account but we're almost there I think.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[louismaximepiton]

With the last changes, I'd rather set a global callout on badges to avoid hiding everything.
One .nav-underline.nav-justified render is broken.

Revert 4fcd51d if you don't like it.

[julien-deramond]

Thanks a lot for this work. It has been gathered and merged with other modifications in #2625. All participants of this PR will be mentioned as co-authors in it.