Use lock in FileSystems to allow only one thread to update options

[liferoad]

Fix#33965

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[scwhittle]

can we get rid of the atomic filesystem revision if we're synchronizing? It's complicated to think through possible timings

[liferoad]

@kennknowles what do you think about this? is it safe to remove atomic from FILESYSTEM_REVISION?

[scwhittle]

#34011 to fix test failure

[Abacn]

There is already a fix in #32723. For usage outside worker, one should call FileSystems.registerFileSystemsOnce which is already a synchronized method.

[liferoad]

There is already a fix in #32723. For usage outside worker, one should call FileSystems.registerFileSystemsOnce which is already a synchronized method.

Close my PR then.