Answer
Introducing a new component requires updating the environment's solutionset.yaml file to include an active entry for it (something like 'XYZ: true') — if the new component isn't present in solutionset.yaml at all, it's treated as inactive by default, which is exactly why it shows Active:False and doesn't appear in Component Registrations. Modifying the Solution Set has to be done as part of a proper delivery, not as an ad-hoc client-side change — a Solution Set update typically flows through the standard sales/Build Place delivery process rather than being something you toggle directly in the running environment.