Bump action versions and update docs workflow trigger

[jessicasyu]

Housekeeping on some workflow action versions:

• Unpin ruby/setup-ruby (which should fix the current failing docs job on main)
• Bump mikepenz/release-changelog-builder-action to v5.0.0
• Fix trigger for docs badges job to always run (currently skipped if a previous job fails)
  • This should correctly generate a "failing" docs badge
  • Same strategy is used in the build and lint badge jobs
• Add trigger for docs workflow to also run when a release is published
  • This should re-trigger docs after the release workflow finished to update versions in the docs

[Jannetty]

@jessicasyu is there a way for us to test/verify this locally? All my experiences testing github actions workflows requires just running them a ton, which is not surely advisable for a release workflow. This all looks good and makes sense to me but I have not run it.

[jessicasyu]

@Jannetty I don't have a great answer unfortunately. I usually use a personal "sandbox" repo to test actions when making big changes. For small changes like this, as long as the changes make sense and don't have any glaring syntax errors, I think the easiest is just to try and see what happens.

[cainja]

Just to add to this thread, I think most of the ways to "test" github CI is kind of clunky and unnecessary for our purposes - i.e. we're not deploying CI/CD to production so I'm okay with it passing a gut check as long as the people who ultimately merge are paying attention.