Previously, when an authenticated Docker builder registry was
configured in the Maven or Gradle plugin and the builder and run
images specified different registries, the authentication credentials
would be sent to both registries. This could cause confusion if both
registries don't recognize the same credentials. This commit enforces
that both images are in the same registry when authentication
is configured.

Fixes gh-24552

Throw an `InvalidConfigDataPropertyException` if bad properties are
detected in profile specific files. The following properties will now
trigger an exception if used in a profile specific file:

	`spring.profiles.include`
	`spring.profiles.active`
	`spring.profiles.default`
	`spring.config.activate.on-profile`
	`spring.profiles`

Prior to this commit, profile based properties in a profile specific
file would be silently ignored, making them hard to find.

Fixes gh-24733

* gh-24789:
  Polish "Upgrade to Gradle Enterprise Maven Extension 1.8.1"
  Upgrade to Gradle Enterprise Maven Extension 1.8.1

Closes gh-24789

See gh-24789

See gh-24789

Closes gh-24790

Fixes gh-24624

Closes gh-24787

* gh-24767:
  Upgrade to Gradle Enterprise Gradle Plugin 3.5.1

Closes gh-24767

See gh-24767

Closes gh-24783

Fixes gh-24782

Closes gh-24765

Closes gh-24766

Closes gh-24781

Closes gh-24780

Closes gh-24779

Closes gh-24778

Closes gh-24777

Closes gh-24776

Closes gh-24775

Closes gh-24774

Closes gh-24773

Closes gh-24772

Closes gh-24771

Closes gh-24770

Closes gh-24768

Fixes gh-24618

Closes gh-24764

Closes gh-24763

Closes gh-24762

Closes gh-24761