chore: remove in-solidarity bot configuration and references

CONTRIBUTING.md

@@ -38,7 +38,6 @@
  checks
 - All projects are listed in [CODEOWNERS](./CODEOWNERS) and [README](./README.md)
 - Contributor License [Agreement](https://opensource.google/docs/cla/)
-- In [Solidarity](https://developers.google.com/style/inclusive-documentation)
 - [Pipelines](./PIPELINES.md)
 - Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
   standards to tell the release automation which [SemVer](https://semver.org/)

PIPELINES.md

@@ -65,11 +65,11 @@ The pipeline context also has the `gcloud` context of a serviceaccount user
 ## Static Checks
 
 Static code checks such as [Mega Linter](https://megalinter.github.io/)
- and [In Solidarity](https://github.com/apps/in-solidarity) are part of the
- linter workflow. They do not need to be included in your pipeline script. We
- recommend you allow the DevRel [workflows](.github/workflows) to automatically
- run on your fork as this is simpler than running locally. In case the workflows
- are disabled, you can manually enable them again as described [here](https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow).
+ are part of the linter workflow. They do not need to be included in your
+ pipeline script. We recommend you allow the DevRel [workflows](.github/workflows)
+ to automatically run on your fork as this is simpler than running locally. In case
+ the workflows are disabled, you can manually enable them again as described
+ [here](https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow).
  We don't mind if the Pull Request fails at first due to these checks!
 
 ## GitHub Pages

README.md

@@ -15,8 +15,6 @@
   limitations under the License.
 -->
 
-[![In Solidarity](https://github.com/jpoehnelt/in-solidarity-bot/raw/main/static//badge-flat.png)](https://github.com/apps/in-solidarity)
-
 Common solutions and tools developed by Apigee.
 
 ## References