RefreshScode refresh mechanism is not safe

Is your feature request related to a problem? Please describe.

@RefreshScope may not be secure enough as it will first destroy the current bean and then create a new bean. What if the environment properties encounter an exception when creating a new bean? This online running application will be a disaster.

Describe the solution you'd like

Is it possible to adjust the order and first try creating a temporary bean? If it can be initialized normally, then replace the original bean. This will be a significant optimization for runtime configuration updates.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

In addition，if it is possible to move @RefreshScope from spring-cloud to spring boot? it should not be bundled to spring cloud project.

I am a core builder in the Nacos community (https://nacos.io/en/) which is widely used by chinese developer community and I am responsible for config center.
We want to implement all configurations on the hosted application side, support elegant updates during runtime, and improve the efficiency of business software iteration. If Spring can support elegant refresh beans, then there is no need for every second party middleware to implement this feature

Start by tracing the @RefreshScope lifecycle in the spring-cloud project, focusing on how environment properties are applied and how the current bean is destroyed and recreated. Compare that behavior with the requested temporary-bean replacement and consider the separate request to move @RefreshScope into Spring Boot. Done would require an agreed design and verified safe runtime refresh behavior.