Fix creation-defer-length extension for all stores

[Murderlon]

Supersedes #283

[mitjap]

I'd rename getOffset to getMetadata and create new function setMetadata or updateMetadata to modify existing metadata. In index.d.ts we need to modify IFile and add property size: number. With this ready this issue should be easy to fix :)

[mitjap]

This PR is almost complete. All that is needed is to implement declareUploadLength on S3 and GCS datastores and enable tests via shared.shouldDeclareUploadLendth().

Any idea why status 412 is sent when upload-length does not match? I think this error code is not appropriate and 400 would be much better.

INVALID_LENGTH: {
        status_code: 412,
        body: 'Upload-Length or Upload-Defer-Length header required\n',
    },

@Murderlon sorry for taking over this PR without consulting you. 😊

[Murderlon]

Any idea why status 412 is sent when upload-length does not match? I think this error code is not appropriate and 400 would be much better.

Yes we can change that, tus also does this:
https://github.com/tus/tusd/blob/6ca6ef69a21c60dc0d00bfc55c4a34fc6398cf1b/pkg/handler/unrouted_handler.go#L60:2

[Murderlon]

I'll take a look at the S3 and GCS ones

[Murderlon]

Thanks for improving this too. I added it to S3 and GCS too. Two things:

• We have a race condition in CI when running the tests in parallel across node versions. It seems the CRUD operations against GCS don't allow these parallel changes and we get rate limited. Not sure what to do about that, I'm considering testing against one node version for now.
• Was quite confused for an hour that GCS has the very unobivous behavior when setting some meta data value to undefined, it actually ignores that and holds the previous value..

EDIT: I disabled parallel jobs in 43c45b7, which seems to help with rate limiting.

Regardless, this PR should be ready

[Murderlon]

Merged it as I have more time for tus-node-server and I want to run a TS migration script without too many conflicts. Review still welcome, I can make the changes in a separate PR. I'll wait another day with releasing this in case you have feedback.

[mitjap]

I have no further comments. I think this can be released, 0.8.0 would be appropriate as there are some breaking changes.