build(deps): update dependency org.codehaus.mojo:flatten-maven-plugin to v1.7.3

[lqiu96]

Update flatten plugin to v1.6.0+ to take advantage of the newly introduced skip flag in v1.6.0. Opt for an older version of the flatten plugin that is relatively stable without many version of bug fixes.

Optionally upgrade to the latest v1.7.x version which has been stable for ~1 year

Why upgrade from Gemini

1.6.0 Context & Issues:

• flatten.skip Support: 1.6.0 added the flatten.skip flag (PR In ServiceApi classes, fix wording of documentation about returning errors vs throwing exceptions. #385)
• Regressions in 1.6.0: However, 1.6.0 had parent dependency resolution issues (such as Issue Update Releasing docs to add "wait for artifact deployment" step #377, where dependencies declared in parent POMs were missing or improperly omitted in flattened POMs) as well as property resolution/interpolation edge cases.

Why 1.7.0+ is the ideal target:

• Fixes Regressions: 1.7.0 explicitly addressed the parent dependency resolution bug (PR DatasetInfo, DatasetId, TableId and Acl models and tests #417) and introduced extended property interpolation (PR Implement client-side buffering for publishing messages #384).
• Retains flatten.skip: 1.7.0 maintains full support for flatten.skip.

1.7.3 is the latest stable release in the 1.7.x branch and includes cumulative bug fixes over 1.7.0:

• 1.7.1: Preserves POM element ordering/formatting in resolveCiFriendliesOnly mode (#446) and updates plexus-interpolation compatibility (#453).
• 1.7.2: Ensures target directories are created reliably and optimizes file operations using Java NIO (#471).
• 1.7.3: Fixes issue where condition-activated profiles were missing from the effective model (#481).

[gemini-code-assist]

Code Review

This pull request updates the flatten-maven-plugin version from 1.3.0 to 1.6.0. The reviewer recommends upgrading directly to 1.7.0 instead, to avoid known regressions and property resolution issues present in version 1.6.0.

[gemini-code-assist]

Since 1.6.0 has known regressions and issues (such as bugs related to property resolution and flattening behavior) which were addressed in subsequent releases, and since 1.7.0 has been stable for a long time (as also noted in the PR description), it is recommended to upgrade directly to 1.7.0 to ensure stability and avoid these known issues.

Suggested change

	<version>1.6.0</version>
	<version>1.7.0</version>