feat(maven)!: use hunt strategy for registries

Switch from "merge" strategy to "hunt" strategy to match with how Maven works.

Closes #22744

BREAKING CHANGE: Maven datasource no longer checks all registries and instead stops when it finds a package in one registry.

lib/modules/datasource/maven/index.spec.ts

@@ -277,27 +277,6 @@ describe('modules/datasource/maven/index', () => {
     expect(res).toMatchSnapshot();
   });
 
-  it('collects releases from all registry urls', async () => {
-    mockGenericPackage({ html: null });
-    mockGenericPackage({
-      base: baseUrlCustom,
-      meta: Fixtures.get('metadata-extra.xml'),
-      latest: '3.0.0',
-      jars: { '3.0.0': 200 },
-      snapshots: [],
-    });
-
-    const res = await get('org.example:package', baseUrl, baseUrlCustom);
-
-    expect(res?.releases).toMatchObject([
-      { version: '0.0.1' },
-      { version: '1.0.0' },
-      { version: '1.0.3-SNAPSHOT' },
-      { version: '2.0.0' },
-      { version: '3.0.0' },
-    ]);
-  });
-
   it('falls back to next registry url', async () => {
     mockGenericPackage({ html: null });
     httpMock

lib/modules/datasource/maven/index.ts

@@ -66,7 +66,7 @@ export class MavenDatasource extends Datasource {
 
   override readonly defaultVersioning: string = mavenVersioning.id;
 
-  override readonly registryStrategy: RegistryStrategy = 'merge';
+  override readonly registryStrategy: RegistryStrategy = 'hunt';
 
   constructor(id = MavenDatasource.id) {
     super(id);