Feature/update apis to v1

[lilachic]

Description

Add /v1 in API urls to adapt backend change.

Related issues

Fixes #826

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (this needs a follow up PR)

Changes Made

The frontend uses now following APIs
"/v1/objects"
"/v1/schemas"
"/v1/validate"
"/v1/submit"
"/v1/submissions"
"/v1/publish"
"/v1/drafts"
"/aai"
"/callback"
"/logout"
"/v1/users"
"/v1/templates"

Added a line about /v1 in API urls in CHANGELOG.
Rename cookie MTD_SESSION to AOIHTTP_SESSION in e2e login test.

Testing

• Unit Tests
• Integration Tests

Mentions

[csc-felipe]

Rebased and pushed, to see test results.

[csc-felipe]

Had to update node, with new npm, same version as github actions, I get the same errors:

$ nvm install 16
$ nvm use 16.15.1
$ node --version
v16.15.1
$ npm --version
8.11.0

[csc-felipe]

Looking at the changes made, I think it still needs something to be done about the routing, and checking that user is logged in. Assuming these were not there before.

[lilachic]

Headless run of the Cypress tests locally fail with login "│ ✖ login.spec.ts ". Locally even e2etest run one by one pass. Running 15 integration tests broke Chrome.
Did not help locally to run npm install with the following versions, the commit "update package-lock.json" 446d3fc:
node-v
v16.14.0
npm -v
8.3.1
So more work with logout, and maybe a new PR for routing.

[lilachic]

The e2e tests to pass need the CSCfi/metadata-submitter#554 merged in the backed develop branch. Locally with that branch the tests passes.

[csc-felipe]

The e2e tests to pass need the CSCfi/metadata-submitter#554 merged in the backed develop branch. Locally with that branch the tests passes.

Done

[lilachic]

No tests fail for getting 400 from v1/schemas/datacite .

[csc-felipe]

No tests fail for getting 400 from v1/schemas/datacite .

I'm sorry, but I didn't understand. Do you mean that /v1/schemas/datacite still gives HTTP 400?