Check application state before showing file resource dialog

[colin-grant-work]

What it does

Fixes #9843 by checking application state before trying to show a file-resource-related dialog.

I think ideally, it wouldn't be the resource that was responsible for this dialog: different contexts should be allowed to handle it differently. But this fix does address the specific problem described in the bug with a minimum change in the architecture. I'm open to other suggestions (for example, maybe if we're running remotely, we should automatically reject rather than automatically approve the request?).

How to test

1. Open the application.
2. Open a binary file or large file of some kind.
3. Observe that you get a dialog requesting confirmation that you want to open the binary file as text.
4. Close and reopen the application.
5. The layout should be restored, and the file should be opened as text without a dialog prompt.

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[msujew]

Just a minor comment: A few of those texts already exist in the nls.metadata.json file.

[vince-fugnitto]

I confirm that the changes work well for me 👍
I verified by:

1. starting the application
2. open a .png with the code editor - prompt is shown
3. reload the application
4. the app starts and properly restores the editor - on master the loading animation would go on forever