feat: deprecate and archive prebuilt bindings for salesforce provider

[team-tf-cdk]

HashiCorp has made the decision to stop publishing new versions of prebuilt Terraform salesforce provider bindings for CDK for Terraform. Once this PR is merged, the cdktf/cdktf-provider-salesforce repository will be archived and will no longer be supported in any way by HashiCorp. Previously-published versions of the prebuilt salesforce provider will still continue to be available on their respective package managers (e.g. npm, PyPi, Maven, NuGet), but these will not be compatible with new releases of cdktf and are no longer eligible for commercial support.

Please complete the following steps in this exact order to complete the deprecation process:

• [ ] Double-check provider.json, sharded-stacks.json, and providersWithCustomRunners.json in this PR for any syntax errors caused by extraneous commas
• [ ] Mark this PR as ready for review and examine the plan output from the checks to confirm the correct resources are destroyed
• [ ] Approve and merge cdktf/cdktf-provider-salesforce#439 and ensure that the release is published to all package managers
  • N.B. New published versions take 6~8 hours to show up in Maven, but you do not need to wait for that, just ensure that the release_maven job completed successfully
• [ ] Manually deprecate the HashiCorp.Cdktf.Providers.Salesforce package in NuGet Gallery (optional but recommended)
  • Provide the following custom message: HashiCorp is no longer publishing new versions of the prebuilt provider for salesforce. Previously-published versions of this prebuilt provider will still continue to be available as installable packages on NuGet, but these will not be compatible with newer versions of CDK for Terraform and are not eligible for commercial support. You can continue to use the salesforce provider in your CDK for Terraform projects with newer versions of CDKTF, but you will need to generate the bindings locally. See https://cdk.tf/imports for details.
• [ ] Remove the "do-not-merge" label and merge this PR

Please also ensure that not too much time passes in between each of these steps. Notably, if the PR in the provider repo is merged but other changes are deployed before that repo is properly archived, there could be unintended behavior. So, it is highly recommended that you complete the above steps in short succession.

[github-actions[bot]]

I'm going to lock this pull request because it has been closed for at least 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue so we can investigate further.