bf(ARSN-361): Handle infinite versionID correctly on version specific PUT for file MD backend

[tmacro]

When passing the infinite versionId (0099999999999999999999RG001) the file backend fails to update the master key if the the infinite version is also the latest version.

[bert-e]

Hello tmacro,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue ARSN-361 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 7.10.48

• 7.70.10

• 8.1.108

Please check the Fix Version/s of ARSN-361, or the target
branch of this pull request.

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/ARSN-361/file_backend_inf_vid into
  development/7.10
• w/7.70/bugfix/ARSN-361/file_backend_inf_vid will be merged into development/7.70
• w/8.1/bugfix/ARSN-361/file_backend_inf_vid will be merged into development/8.1

The following branches will NOT be impacted:

• development/6.4
• development/7.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[jonathan-gramain]

Can you add a test for this new behavior? Even though it's a test backend, we should ensure we don't introduce regressions. For example a simple test inspired by this one would do: https://github.com/scality/Arsenal/blob/development/7.10/tests/unit/versioning/VersioningRequestProcessor.spec.js#L153

[tmacro]

closing this PR since it is no longer needed