Gradle 8 fixes

[felixdesouza]

Before this PR

The way gradle-conjure generates files means that it will run into implicit dependency errors. This was happening in conjure.

After this PR

==COMMIT_MSG==
Set up correct dependencies for Gradle 8.
==COMMIT_MSG==

Key points:

• Instead of using a static directory, use the output of the generator task for the source set
• Set the output to be different for each generator task (java):
  • so instead of src/generated/java, we have build/generated/sources/conjure-<type>/main/java
  • This mirrors what gradle do with annotation processors: build/generated/sources/annotationProcessor/java/main
• Separate out the ide tasks so that running ./gradlew idea or ./gradlew eclipse depends on the umbrella task, but each subproject task

Possible downsides?

Hard to migrate python/typescript/other sources, as I don't know how they are consumed and that would be a break. In fairness the existing code had set up idea to do the wrong thing to them anyway but I imagine people will want to keep stuff in source. This may not fix us for the implicit dependency if we're running into the python/ts errors in

[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

Set up correct dependencies for Gradle 8.

Check the box to generate changelog(s)

• Generate changelog entry

[CRogers]

These write gitignore tasks are also causing task dep validation errors. Maybe not this one specifically, but there are some more internally that also have problems as they get included into source jars without the dependsOn

[svc-autorelease]

Released 5.43.0