[draft] upgrade to terraform provider v5.91.0

[mbbush]

Description of your changes

I choose v5.91.0 because it was the most recent at the time I started. I don't see any reason why I won't update to the most recent again before getting this ready.

The two largest issues I ran into when upgrading the terraform provider version are:

• The upstream terraform provider no longer compiles when the mq_user resource is added. I fixed it with a minor change to the patches, but I don't have a good way to test the resource.
• The s3_bucket_lifecycle_configuration resource was moved from the terraform sdk to the terraform plugin framework. Simply moving its external name configuration caused errors during codegen, so I've removed it completely on this branch. I'm adding it back in [draft] Re-implement s3 bucket lifecycle configuration using framework with new schema #1765, which I may just merge into here once I get it working.

Still TODO (among other things)

• Add back the s3 bucket lifecycle configuration resource and test it
• Validate/document the behavior of existing s3 bucket lifecycle configuration resources during a provider version upgrade. Given the reasons behind the terraform provider re-implementation (AWS api changes that couldn't be correctly handled with the sdk: I think it had something to do with nullability) there may be some nuance here.
• Check for schema changes in other resources
• Go through the terraform provider release notes and see if there's anything concerning. If so, validate it.
• Do we need special handling for the write-only version of attributes? Instance.rds and secretsmanager.SecretVersion are examples. It seems like we should probably remove them entirely from the CRDs.

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.

How has this code been tested