fix: properly store the initiatedByPropertyManager in registrations

[JazzarKarim]

Issue:

• Bug: Incorrect 'Completing Party' identified during renewals entity#32154

Description of changes:

• Look in the registrations_json, if the initiatedByPropertyManager is found, store it in the registration under property manager

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the BC Registry and Digital Services BSD 3-Clause License

[JazzarKarim]

@dimak1 @thorwolpert So i found something really interesting. That initiatedByPropertyManager field is populated in the registration_json across ALL registrations. This was done collaterally by the backfiller job that I ran last week. I'm thinking this might fix our problem for CURRENT & OLD registrations. Thoughts?

[thorwolpert]

You should use | None instead of Optional[] going forward.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dimak1]

@JazzarKarim good news if it fixes it. I also found a workaround for PMs during the renewals, so we should be good for now. It is in the ticket.