fix(Component sources): clear reasons and re-enable when component becomes eligible

When a component fails checkRequirements(), its incompatibility reasons are stored and it is disabled. If the component later becomes eligible again (e.g. a prop is fixed), the reasons were never cleared and the component was never re-enabled, even though the config entity was otherwise correct.

• Clear auto-disable reasons for eligible components during generation.
• Respect manually-disabled components: reasons of ['Manually disabled'] are left intact and the component remains disabled.

Issue: #3585530

Closes #3585530