feat(ci): create reusable changelog generation

[heitorlessa]

Issue number: #1398

Summary

Changes

Please provide a summary of what's being changed

This PR introduces a reusable workflow to update changelog, and correct permissions that made release failed last time - both related to the introduction of changelog generation.

Tasks

• include changelog generation on docs build
• update release automated activities docs
• add additional release input to accurately describe intent on skip
• job permissions
• read changelog step on release
• create reusable changelog workflow
• update rebuild latest doc workflow to use new changelog worklfow
• correct race condition when files are changed halfway through changelogs are pushed

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[heitorlessa]

thank you @rubenfonseca. Merging