Make implementation fully Microsoft-compliant

[glpatcern]

The Microsoft 365 cloud services provide since long time an up-to-date, GUI-based WOPI validation test suite. Most tests pass or are skipped because of missing capabilities, but a few fail and should be fixed.

In particular:

• CheckFileInfoSchema.HostUrls -> addressed by Enable compliant host URLs in CheckFileInfo #93
• FileVersion -> addressed by Use the etag for WOPI versions #62
• PutUserInfo
• PutRelativeFile.RelativeNameConflictOverwriteFalse
• PutRelativeFile.FileNameLongerThan512Chars
• PutRelativeFile.IncludeHostUrls
• PutRelativeAndRenameFile.RenameShouldSucceed
• PutRelativeAndRenameFile.FileNameAfterRenameIsCorrectlyEncoded
• PutRelativeAndRenameFile.RenamingALockedFileWithACorrectLockHeaderValueShouldSucceed
• PutRelativeAndRenameFile.RenameShouldNotChangeFileExtension
• FileUrlUsage
• ProofKeys.CurrentInvalid.OldValidSignedWithOldKey
• ProofKeys.CurrentInvalid.OldInvalid
• ProofKeys.TimestampOlderThan20Min

[glpatcern]

This is the current state with version 8.2.0 and after enabling renames:

The 4 failing tests with rename operations are all due to the same issue, that is the wopiserver is largely based on filenames for its operations and should use the fileid instead.

[glpatcern]

Current state of the test suite with rename operations disabled:

[glpatcern]

As part of the tests for #94, some broken cases were found and fixed on single-file shares, which after #97 cannot execute PutRelative and would trigger the PutRelativeUnsupported group of tests. This is now fixed: