Ensure Tab keyboard functionality after #37146

[GeoSot]

Description

After
1510c25.
https://twbs-bootstrap.netlify.app/docs/5.2/components/navs-tabs/#javascript-behavior,

@julien-deramond pointed out:

The user for navigating between the tabs has to do the following:

• Press "Tab" -> "Home" is focused
• Press "Right" -> "Profile" is selected (not really focused with the blue outline)
• Press "Tab" -> "Profile" is focused
• Press "Right" -> "Contact" is selected (not really focused with the blue outline)
• Press "Tab" -> "Contact" is focused

/cc @patrickhlauke

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (non-breaking change)
• Breaking change (fix or feature that would change existing functionality)

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-37200--twbs-bootstrap.netlify.app/docs/5.2/components/navs-tabs/#javascript-behavior

[julien-deramond]

I haven't followed the topic around 1510c25 but I can confirm that this PR fixes the behaviour mentioned in the description and is back to normal as it was in the v5.2.

[patrickhlauke]

confirming that, based on the live preview, this works as it should. assuming that this does not reintroduce the problem noted in #37107, and that the JS tests all still make sense, this looks good to me

[julien-deramond]

LGTM! The keyboard behavior is fixed 🚀
@GeoSot I've added some focus spies in 2 other unit tests in df6485b (with the disabled states) just to add some extra-security. If you think it is unnecessary you can remove this commit :)