Upgrade Bootstrap from version 3 to 5.

[sayravai]

Description

What?

Upgrade of the Bootstrap UI library from version 3 to 5.

Why?

Bootstrap 3 is no longer receiving security or other updates. We thought about migrating to another UI library, but decided to do a version upgrade instead at this time, and look at possible bigger architectural changes later on.

How?

The templates, CSS, and JavaScript have been updated to work with the new Bootstrap version. Although jQuery is no longer required for Bootstrap, there are many other things that use or require it, so migrating off that was not attempted. Some functions were converted to plain JS, though.

Some other things updated/changed in this PR:

• The Glyphicon font was replaced by Bootstrap icons.
• The DataTables plugin was upgraded from version 1 to 2.

Things to look into still:

• Grader feedback/protocol and old course materials (icons, removed Bootstrap 3 components like panels).
• A-plus RST tools (https://github.com/apluslms/a-plus-rst-tools/); currently this produces output for use with Bootstrap 3.
• Alert box colors do not quite match the previous ones (not sure if this is an issue or not).
• Checking for possible accessibility issues introduced by the upgrade.
• A-plus-button classes: should these be updated further to better match the new BS5 look?
• The Bootstrap Multiselect (http://davidstutz.de/bootstrap-multiselect/) jQuery plugin does not support Bootstrap 5 so, for the time being, I borrowed modified plugin code found at https://github.com/SuffolkLITLab/docassemble-ALToolbox/blob/main/docassemble/ALToolbox/data/static/bootstrap-multiselect.js . This plugin is used only at the All Results page.

Testing

Remember to add or update unit tests for new features and changes.

• How to test your changes in A-plus
• How to test accessibility

What type of test did you run?

• Accessibility test using the WAVE extension.
• Django unit tests.
• Selenium tests.
• Other test. (Add a description below)
• Manual testing.

All Playwright tests were updated and ran.

[ADD A DESCRIPTION ABOUT WHAT YOU TESTED MANUALLY]

Did you test the changes in

• Chrome
• Firefox
• This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken

Translation

• Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

• Did you follow our style guides?
• Did you use Python type hinting in all functions that you added or edited? (type hints for function parameters and return values)

Have you updated the README or other relevant documentation?

• documents inside the doc directory.
• README.md.
• Aplus Manual.
• Other documentation (mention below which documentation).

Is it Done?

• Reviewer has finished the code review
• After the review, the developer has made changes accordingly
• Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!