Inconsistent URL versioning

Context & Scope

The following endpoints have both v1/v2 in their path which is not a clear API versioning

• /api/file/v2/v1/files/{id}/downloadURL
• /api/file/v2/v1/files/uploadURL
• /api/file/v2/v1/files/metadata
• /api/file/v2/v1/files/{id}/metadata

Decision

Change the Above APIs respectively

• /api/file/v1/files/{id}/downloadURL
• /api/file/v1/files/uploadURL
• /api/file/v1/files/metadata
• /api/file/v1/files/{id}/metadata

Rational

Consistent and clear API versioning.

Consequences

Users of these APIs need to change the paths for above APIs

Impact

The changes would be in core module and no needed for CSPs to change any code