Update repo settings to streamline Csur

[bbenligiray]

If CI passes and only contents of certain directories are changed, it would be safe for non-codeowners to release. This would streamline Csur.

[Siegrift]

Not sure how you envision this to work during the CI releases, but alternative way would be to utilize GitHub CODEOWNERS to allow merging PRs that only change certain files/folders.

The releases could then be automated via CI (and they would require the tests to pass).

This would streamline Csur.

This is also important for dApp integrations.

[bbenligiray]

Yeah I was planning to use that

[hiletmis]

An average Csur experience is like following:

• Updates data folder:
  • Adds chain configuration file
  • Adds support for new chain chain-support.json
• Updates deployments folder:
  • Adds chain contract deployments
  • Updates deployment addresses addresses.json
• Updates @api3/contracts package:
  • Minor package release
  • New chains are included chains.ts

Following files can be owned by a secondary owner:

• chain-support.json
• chain.ts

Following folders also should be owned by a secondary owner:

• data/chains
• deployments
• .changeset

Additionally a Csur workflow can be added to check if applied changes are legit. Not sure how and when this CI will be triggered ATM. But sounds doable

[bbenligiray]

It will also update CHANGELOG.md and package.json.

Additionally a Csur workflow can be added to check if applied changes are legit. Not sure how

Some attacks I can imagine right now can be detected by cross-checking against an external source such as chainlist. However, I'm not sure that every possible attack is covered. Assuming we won't do a lot of chain checklists in the future, maybe it's safer to let this remain as is.

[hiletmis]

It will also update CHANGELOG.md and package.json.

I didn't add them on purpose but then realized that they are modified by GitHub-Actions bot which makes things more complicated and prone to abuse