cephfs: upgrade fscrypt version to fix concurrency issue (backport #4609)

[mergify]

In older versions of fscrypt there is a race condition when multiple encrypted cephfs instances are deployed simultaneously.
This PR upgrades the fscrypt version to the latest version that contains a fix to the concurrency issue, used the commit sha as we cannot know when the next official release will happen from fscrypt side.

This PR fixes: #4592

---

This is an automatic backport of pull request #4609 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 3073409 has failed:

On branch mergify/bp/release-v3.11/pr-4609
Your branch is up to date with 'origin/release-v3.11'.

You are currently cherry-picking commit 307340969.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   go.sum
	modified:   vendor/github.com/google/fscrypt/actions/context.go
	modified:   vendor/github.com/google/fscrypt/actions/policy.go
	modified:   vendor/github.com/google/fscrypt/crypto/crypto.go
	modified:   vendor/github.com/google/fscrypt/crypto/rand.go
	modified:   vendor/github.com/google/fscrypt/filesystem/filesystem.go
	modified:   vendor/github.com/google/fscrypt/filesystem/mountpoint.go
	modified:   vendor/github.com/google/fscrypt/metadata/config.go
	modified:   vendor/github.com/google/fscrypt/metadata/metadata.pb.go
	modified:   vendor/github.com/google/fscrypt/metadata/policy.go
	modified:   vendor/github.com/google/fscrypt/security/privileges.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   vendor/modules.txt

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[NymanRobin]

I will look at this and try to resolve it manually

[NymanRobin]

The PR is now open at #4613, so this can be closed? Hopefully this was okay, @Madhu-1 let me know in case I missed something?