Should failures in the lazy loading process of beans after refresh also be recorded in errors?

[qnnn]

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

When GenericScope#destroy is executed, it checks the execution result of the bean's destroy callback and records exceptions in the errors map. However, during lazy loading of the bean, the result of bean loading is not checked. Shouldn't we also record bean loading failures in the errors map?

Additionally, can we add an eager switch for refreshing, similar to ConfigurationProperties, to immediately create the bean after destruction? This way, we can determine the refresh result of the bean earlier.

[qnnn]

The implementation for recording bean loading failures in errors already exists.