Finalize repo QA compliance

[BTT21000]

As part of the TM issue https://github.com/api3dao/tasks/issues/849 for QA, some requirements need to be addressed:

Repo setup requirements as per [new_repo_creation_checklist.md]

• Verify Renovate setup for automated security vulnerability scanning to detect vulnerabilities in the codebase and dependencies.

Package setup requirements as per new_package_creation_checklist.md:

@api3/airnode-abi

• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-adapter

• Add if needed prettier and the .prettierrc configuration file
• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-admin

• Add and edit if needed the key configuration files such as .eslintrc, .prettierrc.
• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-deployer

• Add and edit if needed the key configuration files such as .eslintrc, .prettierrc.
• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-examples

• Add and edit if needed the key configuration files such as .eslintrc, .prettierrc.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-node

• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-operation

• Add and edit if needed the key configuration files such as .prettierrc.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-protocol

• Add and edit if needed the key configuration files such as .prettierrc.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-utilities

• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

@api3/airnode-validator

• Add and edit if needed the key configuration files such as .prettierrc.
• Edit the README.md if needed so that it looks well presented on www.npmjs.com, and provides a clear and comprehensive description about the package, including installation instructions, usage examples, and any other relevant information. Package update changesets should not be included in the README.md.
• Add relevant package.json fields if applicable (e.g. such that repo links, description, keywords, and author show up in NPM, compare this to this)

[Siegrift]

@dcroote This is not urgent, so I've un-assigned you from this issue.