[FLINK-37693][state] Avoid reading NOT_OWNED file by local file system when restoring

[masteryhx]

What is the purpose of the change

When forst starts to restore from reused checkpoint, the mapping entries include:

1. remote uuid -> state handle (also remote uuid path in the state handle)
2. remote sst -> remote uuid

When restored, the file is existed, but fails because it always try to find a sst in the local filesystem.
We should avoid reading NOT_OWNED file by local file system when restoring.

Brief change log

• Judge whether the file is NOT_OWNED when trying to access local file system.

Verifying this change

• Added ForStFlinkFileSystemTest#testNotOwnedFileStatus

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
• The serializers: (yes / no / don't know)
• The runtime per-record code paths (performance sensitive): (yes / no / don't know)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
• The S3 file system connector: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[masteryhx]

@AlexYinHan Kindly ping

[flinkbot]

CI report:

• d82cc3f Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[AlexYinHan]

@masteryhx Thanks for reporting and fixing this. LGTM. A NOT_OWNED file must be an SST file, so we can use file ownership to provide supplementary information for determining whether a file should be local.