#6945568 Domains: Skip domain lock verification for inbound transfers when lock cannot be determined

Changes proposed in this Pull Request

This PR fixes the issue described in p2MSmN-8N0-p2, where a user wasn’t able to initiate an inbound domain transfer because its lock couldn’t be determined and came as null – this is not an uncommon situation, as there are a variety of reasons why a domain lock might not be determined.

This PR updates the transfer flow to allow skipping the lock verification in those cases, as shown in the screenshot:

Testing instructions

Try to find a pending domain transfer whose lock cannot be determined. Alternatively, sandbox public-api and hack the /domains/<mygroovydomain.com>/inbound-transfer-status endpoint to return the following data:

return [
	'admin_email' => null,
	'creation_date' => null,
	'in_redemption' => null,
	'privacy' => true,
	'registrar' => null,
	'registrar_iana_id' => null,
	'term_maximum_in_years' => 10,
	'transfer_eligible_date' => null,
	'transfer_restriction_status' => "not_restricted",
	'unlocked' => null,
];

Try to initiate a domain transfer in these conditions and ensure you’re able to skip the domain lock verification step as shown in the screenshot.