Remote ID FAA: Operator ID invalid on reboot or app restart

[jnomikos]

Description

1. If in FAA jurisdiction, operator ID will be invalidated on app restart or vehicle reboot (if not correct under EU jurisdiction) because there's a validity check in the constructor which checks if the operator ID is valid under EU jurisdiction even if in FAA.

2. If vehicle is rebooting and you are in the Remote ID app settings page, the quick refresh of the page is detected as a text field change and can be detected as operator ID being changed. Make it so it tracks if the text field is being focused.

Test Steps

1. Have remote ID enabled
2. Make sure FAA is the jurisdiction and assign an operator ID that would be invalid in EU jurisdiction like "John"
3. Either reboot the vehicle or close app and reopen
4. Witness operator ID stay valid
5. Next, reboot vehicle in param page and go to remote id page as vehicle loads back up
6. Ensure operator id doesn't change

Checklist:

• Review Contribution Guidelines.
• Review Code of Conduct.
• I have tested my changes.

Related Issue

#13377

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[DonLakeFlyer]

@jnomikos Is this important enough to cherry pick to stable as well?

[jnomikos]

@jnomikos Is this important enough to cherry pick to stable as well?

In my opinion, it isn't important enough to cherry pick since operator ID is technically not required by FAA.