fix: Ensuring Region.Logger is set before navigation proceeds

[nickrandolph]

GitHub Issue (If applicable): #1732

PR Type

What kind of change does this PR introduce?

• Bugfix

What is the current behavior?

Region.Logger isn't set if startup takes too long

What is the new behavior?

Region.Logger is always set before nav takes place

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

[Youssef1313]

Small comment on TCS usage, but other than that LGTM

[nickrandolph]

@Mergifyio backport legacy/2x

[mergify]

backport legacy/2x

✅ Backports have been created

• #1734 fix: Ensuring Region.Logger is set before navigation proceeds (backport #1733) has been created for branch legacy/2x but encountered conflicts