feat: update Bootstrap to v4.5

[jacobmllr95]

Describe the PR

This PR bumps the suggested Bootstrap version to v4.5.

TODO:

• Check if there are any required changes

PR checklist

What kind of change does this PR introduce? (check at least one)

• Bugfix (fixes a boo-boo in the code) - fix(...), requires a patch version update
• Feature (adds a new feature to BootstrapVue) - feat(...), requires a minor version update
• Enhancement (augments an existing feature) - feat(...), requires a minor version update
• ARIA accessibility (fixes or improves ARIA accessibility) - fix(...), requires a patch or minor version update
• Documentation update (improves documentation or typo fixes) - chore(docs), requires a patch version update
• Other (please describe)

Does this PR introduce a breaking change? (check one)

• No
• Yes (please describe since breaking changes require a minor version update)

The PR fulfills these requirements:

• It's submitted to the dev branch, not the master branch
• When resolving a specific issue, it's referenced in the PR's title (i.e. [...] (fixes #xxx[,#xxx]), where "xxx" is the issue number)
• It should address only one issue or feature. If adding multiple features or fixing a bug and adding a new feature, break them into separate PRs if at all possible.
• The title should follow the Conventional Commits naming convention (i.e. fix(alert): not alerting during SSR render, docs(badge): update pill examples, chore(docs): fix typo in README, etc). This is very important, as the CHANGELOG is generated from these messages, and determines the next version type (patch or minor).

If new features/enhancement/fixes are added or changed:

• Includes documentation updates
• Includes component package.json meta section updates (prop, slot and event changes/updates)
• Includes any needed TypeScript declaration file updates
• New/updated tests are included and passing (required for new features and enhancements)
• Existing test suites are passing
• CodeCov for patch has met target (all changes/updates have been tested)
• The changes have not impacted the functionality of other components or directives
• ARIA Accessibility has been taken into consideration (Does it affect screen reader users or keyboard only users? Clickable items should be in the tab index, etc.)

If adding a new feature, or changing the functionality of an existing feature, the PR's
description above includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/bootstrap-vue/bootstrap-vue/977ad4p35
✅ Preview: https://bootstrap-vue-git-feat-bootstrap-v45.bootstrap-vue.now.sh

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 2bb7079:

Sandbox	Source
wandering-fire-il4dp	Configuration

[codecov]

Codecov Report

Merging #5395 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #5395   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          277       277           
  Lines         8875      8875           
  Branches      2495      2495           
=========================================
  Hits          8875      8875           

Flag	Coverage Δ
#unittests	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 33e39b0...2bb7079. Read the comment docs.

[jacobmllr95]

@tmorehouse I've went through all the changes in the Bootstrap v4.5 release and tested the docs and don't see anything we really need to change.

[tmorehouse]

@jackmu95 There might be a few CSS fixes that we have to get around issues in 4.3/4.4 that are not required in 4.5, but if we allow users to use 4.4 (or 4.3) then we probably should leave the CSS fixes in place.

[jacobmllr95]

@jackmu95 There might be a few CSS fixes that we have to get around issues in 4.3/4.4 that are not required in 4.5, but if we allow users to use 4.4 (or 4.3) then we probably should leave the CSS fixes in place.

Yeah, otherwise it would be a breaking change.