[Bug] the new step of each service first migration notice is always the mode which was set at first mode setting

[zrlw]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

dubbo 3.3.4

Steps to reproduce this issue

refer to dubbo-samples/dubbo-servicediscovery-migration

1. start provider1 and provider2 of dubbo-servicediscovery-migration
2. change the name of DemoServiceConfigIT to ADemoServiceConfigIT, run 'All tests' of dubbo-servicediscovery-migration-consumer on IDEA, it will run DemoServiceIT after ADemoServiceConfigIT just like github actions does.
   sometimes Assert.assertTrue(demoServiceFromService.sayHello("client").contains("registry-type: service")); at DemoServiceIT#testApplication might throw no provider exception because the new step of demoServiceFromService migration notice was set to FORCE_INTERFACE, but it should be APPLICATION_FIRST.
   see details at https://github.com/apache/dubbo-samples/actions/runs/15293293194/job/43016875948
   

What you expected to happen

the new step of each service first migration notice should be the step that was set by current test case.

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[zrlw]

the cause might be DemoServiceConfigIT set the same application name with DemoServiceConfigIT.

[zrlw]

it's the sample test issue and should be fixed by apache/dubbo-samples#1215