CSS: $prefix to the whole assets

[louismaximepiton]

Description

Changed bs- to #{$prefix}.

Motivation & Context

Feel like it will ease the work on some forks for folks since they won't need to change every bs- in the scss files if they use a different prefix.
Following the additions done in #35857 in assets/brand for example.

Type of changes

• Refactoring (non-breaking change)

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
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Live previews

• https://deploy-preview-39617--twbs-bootstrap.netlify.app/

Related issues

NA

[julien-deramond]

I haven't looked at the details of this PR yet (thanks @louismaximepiton btw) but was there a technical reason @twbs/css-review for having --bs in site/assets/scss/ instead of using the prefix? Seems to be there voluntarily.

[ffoodd]

Docs aren't initially meant to be customized, I guess. I think we had this discussion when we first introduced custom properties in the docs.

[julien-deramond]

I'll try to look at it asap but the original idea of the PR bs- to #{$prefix} is interesting. Even if our doc is not meant to be customized, since it is compiled in this same project, having #{$prefix} could help while searching for patterns. But I might missing something here.

[mdo]

I've always wanted to treat the docs as a project using Bootstrap, so that's why I went with the typed out prefix. But I'm fine going either way, ultimately doesn't matter at all to the output or anything else :).

[julien-deramond]

Based on mdo's feedback, let's continue with the same approach in our doc. Thanks @louismaximepiton for your PR. LGTM!