Add Jackson packages grouping to Renovate configuration and fix gitignore

[Copilot]

This PR adds a grouping rule to the Renovate configuration to combine Jackson dependency updates into a single PR instead of creating separate PRs for each Jackson package. Also removes build-scan.txt file and adds it to .gitignore to prevent Gradle build scan URLs from being committed.

Problem

Currently, Renovate creates separate PRs for different Jackson packages, as seen in:

• PR fix(deps): update dependency com.fasterxml.jackson.core:jackson-databind to v2.20.0 - autoclosed #2228: Updates com.fasterxml.jackson.core:jackson-databind to v2.20.0
• PR fix(deps): update dependency com.fasterxml.jackson:jackson-bom to v2.20.0 - autoclosed #2227: Updates com.fasterxml.jackson:jackson-bom to v2.20.0

This creates unnecessary review overhead when Jackson releases new versions that affect multiple packages simultaneously.

Solution

Added a new package rule to group all com.fasterxml.jackson{/,}** packages together:

{
  groupName: 'jackson packages',
  matchPackageNames: [
    'com.fasterxml.jackson{/,}**',
  ],
},

This follows the existing pattern used for other grouped packages like spotless packages, errorprone packages, and hipparchus packages.

Additional Changes

• Removed build-scan.txt file which contained Gradle build scan URLs that should not be committed
• Added build-scan.txt to .gitignore to prevent future accidental commits of build scan files

Impact

• Future Jackson updates (jackson-bom, jackson-core, jackson-databind, etc.) will be combined into a single PR
• Reduces review overhead and ensures consistent Jackson version updates across the project
• Matches the existing dependency management strategy where Jackson BOM is used to align versions
• Prevents build artifacts from being accidentally committed to the repository

The pattern com.fasterxml.jackson{/,}** will match all Jackson packages currently used in the project, including:

• com.fasterxml.jackson:jackson-bom
• com.fasterxml.jackson.core:jackson-core
• com.fasterxml.jackson.core:jackson-databind

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[breedx-splk]

So this feels like copypasta (it's even in the docs), but maybe I'm missing something and I am willing to use this as a moment to learn.

Java doesn't use the forward slash in package names, so why does this glob include a forward slash?

My understanding of the brace expansion is that com.fasterxml.jackson{/,}** simply expands to com.fasterxml.jackson/** com.fasterxml.jackson**. Right?

So we don't need that first one, and the second one is probably overkill. Jackson packages are just in com.fasterxml.jackson so I'd prefer that this just tighen up to com.fasterxml.jackson. If there are other packages in the future that we want to add, we can do that then.

Suggested change

	'com.fasterxml.jackson{/,}**',
	'com.fasterxml.jackson',

[trask]

com.fasterxml.jackson.core:jackson-databind is in com.fasterxml.jackson.core

[breedx-splk]

Can we still be explicit then and avoid the forward slash thinger?

Suggested change

	'com.fasterxml.jackson{/,}**',
	'com.fasterxml.jackson',
	'com.fasterxml.jackson.core',

[trask]

looking into the question about {/,}... I'm not sure (other than it's the pattern we use elsewhere in this file)...

[trask]

yeah, from the Renovate logs, it looks like

"packageName": "com.fasterxml.jackson.core:jackson-databind"

can I make a follow-up PR to fix this since copilot did its job here based on our current pattern?