Remove opsworks provider that is now EOL

[mbbush]

Description of your changes

On May 26, 2024, AWS completed their deprecation cycle for the opsworks service and it is now completely EOL for both new and existing customers. Nobody can use it anymore.

This removes the resources from the provider to shrink our maintenance burden, build time, image sizes, etc.

Fixes #1224

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

[haarchri]

can we add a message in Release Notes that people can remove the CRDs for opsworks ?

[mbbush]

Maybe we release this in the same version that stops shipping the monolithic provider? It's definitely worth mentioning in the release notes, but given what I've learned about opsworks while reading the deprecation docs, I'd be somewhat surprised if anyone is installing provider-aws-opsworks.

[github-actions]

This provider repo does not have enough maintainers to address every pull request. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.