Add new labels and standardise labels across all repos

[GuySartorelli]

We currently don't have a "type" label for various cards, such as spikes or administrative tasks. We should implement a "type/other" label for this purpose.

We should also add a "affects/v6" label in preparation for working on Silverstripe CMS 6.

Documentation for labels is at https://docs.silverstripe.org/en/contributing/issues_and_bugs/#labels

NOTES

• The "affects" labels are for things that actually do affect that version. i.e. there is no v6 yet, so there should be nothing using the "affects/v6" label yet.
  • To mark cards as needing to be implemented in a new major release, the "type/api-break" label should be used.
  • This is because if we added "affects/v6" to a bunch of cards and then don't implement changes for those cards, we end up with outdated labels on those cards.
  • The definition already states "Issue has been observed on a specific CMS release line" so that might be sufficient

Acceptance criteria

• A new "type/other" label is added and documented (document in cms 4 and 5 docs)
• A new "affects/v6" label is added
• The labels documentation is updated to more clearly indicate the purpose of the "affects" labels.
• A script is added to the module standardiser to standardise labels, and that script is run across all repositories we care about

Note

• We will create the affects/v6 label once we start actively working on CMS6.

PR

• NEW Update GitHub labels module-standardiser#29
• DOC Add description for type/other label and clarify affects labels developer-docs#446
• FIX Init array, use $oldName, add REPOS_EXCLUDE, check if label exists before rename module-standardiser#30

[GuySartorelli]

Capability added - reassigning to steve to roll out across repos

[GuySartorelli]

PRs merged, all steps completed