Add default includeAllJdks option to generateGradleJdkConfigs

[crogoz]

Before this PR

After this PR

In preparation for https://github.com/palantir/gradle-jdks/pull/479/files#diff-53f3309ab573fe65d62f8b5bf40e9bb94478d82b4d6434cb6bcf9b25516813a4R79. That PR will only install & configure only the jdk versions used. Because of this, excavators that bump the java versions (eg. https://pl.ntr/2q1), would need to pre-install extra java versions. For this, I have added the command line option ./gradlew generateGradleJdkConfigs --includeAllJdks that will generate all the jdk configuration files.
In this PR, the addition is a noop. It only allows the excavators that update the java versions to use the new command line to ensure they are not broken when https://github.com/palantir/gradle-jdks/pull/479/files is merged.

==COMMIT_MSG==
Add default includeAllJdks option to generateGradleJdkConfigs
==COMMIT_MSG==

Possible downsides?

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Add default includeAllJdks option to generateGradleJdkConfigs

Check the box to generate changelog(s)

• Generate changelog entry