Migrate Bulma to Bootstrap 5

[kaapstorm]

🦖 SAAS-19179

Now with Bootstrap 5!

(This branch is rebased onto master so that it can get merged before the ongoing dashboard work is complete.)

Definitely easier to review by commit 🐡

[nospame]

These surrounding <div>s seem like they're probably not be necessary around the form fields anymore.

[kaapstorm]

It appears that they're intended to keep the input fields below their labels.

[nospame]

Ah, that's fair. If there's a way to apply the form-control class to the inputs themselves that would also do this (and apply a little bit of Bootstrap styling), but not sure there's an easy way for inputs rendered as {{ form.field }}

[kaapstorm]

b6ce3db and 5395b29

[kaapstorm]

Thank you for the thorough review @nospame ! I think (I hope) we're done with this bit. I'll follow up later with a PR with some refactors and optimizations.

Edit: Oh! Wait! There is a little more clean-up to do. One moment ...

[kaapstorm]

Okay, I think that's everything. 😅

[kaapstorm]

Right. This time I think I'm actually done. There may still be some unnecessary <div>s lurking about, but we can clean those up as we find them. And the choice made in commit Widget template for <select> might be debatable, but I think it's the right one for getting styling out of the backend.

[nospame]

Just noting that when using prettier (as added in a different PR) it will tend to compress spaces between template tags, so this class attr would probably come out without any spaces, like this:

"form-select{% if widget.attrs.class %}{{ widget.attrs.class }}{% endif %}"

Spaces before template tags or after are maintained, so this would be untouched:

"form-select {% if widget.attrs.class %}{{ widget.attrs.class }}{% endif %}"

[kaapstorm]

Thank you!