[gomod] Deprecate the '--force-gomod-tidy' CLI flag

[eskultety]

This deprecates the --force-gomod-tidy CLI option. Since this effort could result in a controversial breaking behaviour the first attempt is somewhat conservative in that it doesn't default to using go mod tidy at all and instead ignores this aspect of a misconfigured repository.

Relates to: #713

Maintainers will complete the following section

• Commit messages are descriptive enough
• Code coverage from testing does not decrease and new code is covered
• Docs updated (if applicable)
• Docs links in the code are still valid (if docs were updated)

Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:

• approve GitHub Actions workflows by clicking a button
• approve the Red Hat Trusted App Pipeline container build by commenting /ok-to-test
  (as is the standard for Pipelines as Code)

[eskultety]

With the Go 1.22 vendored workspaces out of the way, this is now rebased and ready for review to make progress with #707 which is a major issue since it only really exists with our Go backend even though Yarn backends are the only ones using temporary repo working copies at the moment.

[eskultety]

Just a note to myself, we'll need to mention this in the release notes as a breaking change because we won't be defaulting to the go mod tidy behaviour after this PR so if any consumer actually made use of the --force-gomod-tidy flag, they'll be left without an alternative on our side (for the record, it was a mistake we allowed this to be configurable and done on our side in the first place since go mod tidy relates to the source repository configuration and setup, not actually building it).