* Support floating labels on `.form-control-plaintext`

* Update floating-labels.md

* Apply suggestions from code review

Co-authored-by: XhmikosR <xhmikosr@gmail.com>
Co-authored-by: Mark Otto <otto@github.com>

* Add .form-check-reverse modifier class

* Update checks-radios.md

Co-authored-by: XhmikosR <xhmikosr@gmail.com>

Co-Authored-By: Gaël Poupard <ffoodd@users.noreply.github.com>

* @babel/cli                  ^7.16.8  →  ^7.17.0
* @babel/core                ^7.16.12  →  ^7.17.0
* karma                       ^6.3.13  →  ^6.3.15
* karma-rollup-preprocessor    ^7.0.7  →   ^7.0.8
* postcss                      ^8.4.5  →   ^8.4.6
* rollup                      ^2.66.1  →  ^2.67.1
* sass                        ^1.49.4  →  ^1.49.7

extracts config initialization from cycle

Co-authored-by: XhmikosR <xhmikosr@gmail.com>

Fixes #35056

Co-Authored-By: Macallan Camara <44030647+Macinto5h@users.noreply.github.com>
Co-Authored-By: XhmikosR <xhmikosr@gmail.com>

The `gap` utility is described on the [Spacing page][1] but is not
actually mentioned on the [Flex page][2] (apart from the [API
section][3]).

[1]: https://getbootstrap.com/docs/5.1/utilities/spacing/
[2]: https://getbootstrap.com/docs/5.1/utilities/flex/
[3]: https://getbootstrap.com/docs/5.1/utilities/flex/#utilities-api

Co-authored-by: XhmikosR <xhmikosr@gmail.com>

Dropdown: dropdown doesn't document `data-bs-target` option & `parentNode` is ALWAYS the wrapper for toggle & menu

As we use the `dataApiKeydownHandler` only for events that are triggered on `[data-bs-toggle="dropdown"]` or on `.dropdown-menu`, we can ensure that their `parentNode` will ALWAYS be the `.dropdown` wrapper

> You can disable every form element within a form with the `disabled` attribute on the `<form>`.

I really want to be mistaken, because this would be a very useful feature! But I don't believe it's true. I can't find anything about this on MDN Web Docs, and adding the `disabled` attribute to a `<form>` does nothing on any browser in my testing.

The `disabled` attribute on a `<fieldset>` does disable all descendant form controls – perhaps that's where the mixup has come from.

* clean-css-cli   ^5.5.0  →   ^5.5.2
* cspell         ^5.16.0  →  ^5.17.0
* eslint          ^8.7.0  →   ^8.8.0
* hugo-bin       ^0.80.0  →  ^0.80.1
* karma          ^6.3.12  →  ^6.3.13
* rollup         ^2.66.0  →  ^2.66.1
* sass           ^1.49.0  →  ^1.49.4

* Tooltip.js: move `shown` check to method

* Tooltip.js: move Popper's creation to method

* Tooltip.js: merge checks before `hide`

* Tooltip.js: minor refactoring on `toggle` method

* Move cspell to Actions

* Remove the now unused `docs-spellcheck` npm script

Co-authored-by: XhmikosR <xhmikosr@gmail.com>

* Fix visual tests

They broke in #34509

* load bundle.js in visual tests

Co-authored-by: GeoSot <geo.sotis@gmail.com>

* use `en-US`
* scan all markdown files
* ignore dist, rtl and tests files

Reference:

https://jasmine.github.io/tutorials/async

'DEPRECATION: An asynchronous function called its 'done' callback more than once. This is a bug in the spec, beforeAll, beforeEach, afterAll, or afterEach function in question. This will be treated as an error in a future version. See<https://jasmine.github.io/tutorials/upgrading_to_Jasmine_4.0#deprecations-due-to-calling-done-multiple-times> for more information.