[SEDONA-611] Fix writing rasters to S3 on EMR

[Kontinuation]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

• Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-611. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

Fix writing rasters to S3 on EMR by re-using the FileSystem object instead of creating new instances. Re-using the FileSystem instance is a common pattern, while creating new FileSystem instances is prone to errors, since some implementations hold transient state required by follow-up operations, and that transient states cannot be accessed by newly created instances.

How was this patch tested?

Passing existing tests, testing manually on emr-7.1.0.

Did this PR include necessary documentation updates?

• No, this PR does not affect any public API so no need to change the documentation.

[jiayuasu]

@Kontinuation Does this re-introduce this bug?: #1236

I guess not, because this PR does not close hfs connection ever? Is this OK?

[Kontinuation]

@Kontinuation Does this re-introduce this bug?: #1236

I guess not, because this PR does not close hfs connection ever? Is this OK?

It is OK. It is a common pattern to acquire a lazily created FileSystem instance and leave it open, so that it could be reused for other filesystem operations.