chore(ci): refactor more workflows to scope permissions

[dreamorosi]

Description of your changes

This PR follows #1978 and makes additional changes to the workflows, namely:

• remove the contents: write permission from the workflow used to make v2 releases since there's no commit
• remove actions: write from the docs-related workflows - initially I thought this was needed but looking at other workflows that are known to be working (i.e. reusable_export_pr_details) and that also upload artifacts, I don't think it's actually needed
• correct workflow reference in workflow (fixes issue I introduced in previous PR after renaming)
• reduce permission scope of Layers workflow

Related issues, RFCs

Issue number: #1799

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

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.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[am29d]

🚢