Provide a workaround for users that do not have a registration_type

What does this MR do and why?

Provide a workaround for users that do not have a registration_type

• there are users that were created before we started storing the registration_type in the database. Those users will default to a 'free' registration when their registration is blank and that is causing a code error for us and keeping the user from completing registration. We aim to fix that permanently with a backfill in the database, but we want to get this temporary fix out more quicly to help any current users experiencing this.
• We'll have those users skip this company step as a way to do the least amount of assumptions about their intentions.
• see #508393 (closed)

Changelog: fixed EE: true

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

see #508393 (comment 2254297524)

How to set up and validate locally

contrived state that only exists in production. See screenshots of simulation and test coverage.

Related to #508393 (closed)