chore: prepare Go modules for the next release

[mdelapenya]

What does this PR do?

This PR prepares the Go modules to the next v0.19.0 release. And for that:

• we added support for skipping git/curl operations in the release script. This is necessary to support modifying the mod files, only.
• actually update the mod files for next release

For the skip git/curl support, the script now accepts a COMMIT environment variable, taking false as default value. If set to true, any git/curl operation will be indeed performed. At the same time, the DRY_RUN variable controls the script, so if any of them are set (DRY_RUN=true OR COMMIT=false) then the operation won't take effect.

Therefore, performing a release needs:

• pass DRY_RUN=false explicitly.
• pass COMMIT=true, explicitly.

In the case we want to prepare a release, which means updating the Go modules to use the new release:

• pass DRY_RUN=false COMMIT=false, which will modify the files but not commiting them nor pushing the git tags for each module. In consequence, the Go proxy is not invoked with curl. The module files will be updated with the next release, and have to be manually committed and submitted to the repository as part of a PR before producing the release.

Why is it important?

Have consistent dependencies in the Go modules, which need to depend on the new version at the moment the release is created.

[netlify]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	03b0ccb
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-go/deploys/64087fadab02bc000819e363
😎 Deploy Preview	https://deploy-preview-929--testcontainers-go.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication