Remove main.yml and release.yml CI workflows

[leogallego]

I noticed the main.yml GitHub Action is failing on every PR (including mine, #2379) so I dug into it a bit.

The workflow uses ansible-cloud/aap_controller_action@v2.1.6 to provision and tear down a workshop on a remote Automation Controller. Right now it's failing hard because the action's container has stdout_callback=community.general.yaml in its ansible.cfg, and that callback was removed in community.general 12.0.0:

ERROR! [DEPRECATED]: community.general.yaml has been removed.
The plugin has been superseded by the option `result_format=yaml`
in callback plugin ansible.builtin.default from ansible-core 2.13 onwards.
This feature was removed from community.general in version 12.0.0.

I don't think we need this workflow anymore.

Looking at the run history:

• 78 total runs since the workflow was created (May 2025)
• 0 successful runs. It has literally never passed.
• Last modified in February 2024 by @sean-m-sullivan
• It fires on pull_request_target with no path filters, so every single PR (including docs/markdown-only changes) triggers a full workshop provision+teardown cycle against a controller at ${{ secrets.CONTROLLER_HOST }}

This repo has evolved into primarily a landing page / documentation site for workshops. The actual lab content lives in individual repos (rhpds/zt-ans-bu-*, rhpds/ansible-dev-tools-showroom, etc.). Running an infra provisioning test on every PR to this repo doesn't match the current purpose.

release.yml might be worth reviewing too. It's meant to build and publish the ansible.workshops collection to Galaxy, but it has 0 runs ever via Actions. The ansible.workshops collection is at version 2.0.0 on Galaxy (last updated April 2024, ~124k downloads) but was likely published manually. The collection contains 36 roles for workshop provisioning infrastructure (AWS setup, controller population, code-server, network routers, security labs, etc.) and provisioner playbooks (provision_lab.yml, teardown_lab.yml). No plugins. The galaxy.yml dependencies are very outdated (community.general: 4.5.0, awx.awx: 19.4.0). If we're still maintaining the collection, this workflow should probably be fixed and tested. If not, it's dead weight.

Neither main.yml nor release.yml affect the other workflows. jekyll-gh-pages.yml (site deployment to GitHub Pages) is separate and would continue working as-is.

I'd suggest we remove main.yml for sure. For release.yml, let's decide whether the collection is still actively maintained or not, and either fix the workflow or remove it.