Ordering of 'spring.config.import' is inconsistent when defined in environment or system properties

[qnnn]

Description

When spring.config.import is defined in application.properties or application.yml, imported config data contributors are ordered consistently with profile-specific variants according to the PROFILE_SPECIFIC option introduced in #25766 5774ea3#diff-f66c18c64b5580ffa30cf0f1dad18db0dba9a1859b3f48902c6d7835cff0cc6e

However, when spring.config.import is defined via:

• Java system properties
• Environment variables

the resulting contributor ordering differs.

Reproducible Scenario

Directory structure:

/mock
 ├── test1.properties
 ├── test1-myprofile.properties
 ├── test2.properties

When configured in application.properties:

spring.config.import=classpath:mock/test1.properties,classpath:mock/test2.properties
spring.profiles.active=myprofile

The resulting precedence order is:

test1.properties
test2.properties
test1-myprofile.properties

However, when configured via environment variables:

SPRING_CONFIG_IMPORT=classpath:mock/test1.properties,classpath:mock/test2.properties
SPRING_PROFILES_ACTIVE=myprofile

The resulting precedence order becomes:

test1.properties
test1-myprofile.properties
test2.properties

This behavior is inconsistent the expected import ordering semantics described in #25766 (Support profile specific ConfigData imports)

Proposed Fix

This PR wraps contributors originating from environment and system property-based spring.config.import definitions in a dedicated contributor wrapper.

This ensures consistent treatment with file-based imports.

[philwebb]

Thanks very much @qnnn! I've made a few changes to the fix to lean of the existing contributor kinds.