use GradleExec#exec over ProviderFactory#exec

[FinlayRJW]

Before this PR

Had no errorprone to encourage the usage of GradleExec

After this PR

We now have an errorprone to force the usage of GradleExec#exec with updated README

See palantir/gradle-utils#435 (comment) for reference

==COMMIT_MSG==
use GradleExec#exec over ProviderFactory#exec
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

Type (Select exactly one)

• Feature (Adding new functionality)
• Improvement (Improving existing functionality)
• Fix (Fixing an issue with existing functionality)
• Break (Creating a new major version by breaking public APIs)
• Deprecation (Removing functionality in a non-breaking way)
• Migration (Automatically moving data/functionality to a new system)

Description

use GradleExec#exec over ProviderFactory#exec

Check the box to generate changelog(s)

• Generate changelog entry

[changelog-app]

✅ Successfully generated changelog entry!

What happened?

Your changelog entries have been stored in the database as part of our migration to ChangelogV3.

Need to regenerate?

Simply interact with the changelog bot comment again to regenerate these entries.

[kelvinou01]

🎉
I think this is good to go. Let's wait for a review from @CRogers before we merge.

[kelvinou01]

Let's test that this compiles!

[FinlayRJW]

should do thats how its used currently - https://github.com/palantir/gradle-utils/blob/develop/platform/src/main/java/com/palantir/platform/GradleOperatingSystem.java#L33

[FinlayRJW]

marked as DNM until we settle how we want to handle errors (i.e palantir/gradle-utils#435) so we don't roll this out only to have to update later

[stale]

This PR has been automatically marked as stale because it has not been touched in the last 14 days. If you'd like to keep it open, please leave a comment or add the 'long-lived' label, otherwise it'll be closed in 7 days.