[tests-only] [full-ci] adding step for getting bearer token with api

[S-Panta]

Description

This PR adds an implementation for getting bearer tokens using API rather than from UI via login.

Related Issue

• Fixes Getting bearer token for e2e tests using api #11307

Motivation and Context

How Has This Been Tested?

• test environment:
• locally and CI

Screenshots (if appropriate):

Types of changes

• 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 change)
• Technical debt
• Tests
• Documentation
• Maintenance (e.g. dependency updates or tooling)

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[saw-jan]

You have to either remove (if possible) or skip this block of code with this PR:

web/tests/e2e/support/objects/runtime/session.ts

Lines 51 to 64 in f6e3a09

	if (!config.basicAuth) {
	const body = await response.json()
	const tokenEnvironment = TokenEnvironmentFactory(tokenType)
	tokenEnvironment.setToken({
	user: { ...user },
	token: {
	userId: user.id,
	accessToken: body.access_token,
	refreshToken: body.refresh_token
	}
	})
	}
	}

[S-Panta]

You have to either remove (if possible) or skip this block of code with this PR:

web/tests/e2e/support/objects/runtime/session.ts

Lines 51 to 64 in f6e3a09

	if (!config.basicAuth) {
	const body = await response.json()
	const tokenEnvironment = TokenEnvironmentFactory(tokenType)
	tokenEnvironment.setToken({
	user: { ...user },
	token: {
	userId: user.id,
	accessToken: body.access_token,
	refreshToken: body.refresh_token
	}
	})
	}
	}

If this line is removed, PR fails on keycloak test because the login flow still holds true for that. Currently, this fixed is directed to fix the pagination feature file. We do no login in pagination and therefore this code isn't initiated.
If I am not mistaken, this is the drone error when I tried to deleted that line https://drone.owncloud.com/owncloud/web/46616/18/13

[saw-jan]

If this line is removed, PR fails on keycloak test because the login flow still holds true for that. Currently, this fixed is directed to >fix the pagination feature file. We do no login in pagination and therefore this code isn't initiated.

yeah, that's why I gave you an option.

You have to either remove (if possible) or skip this block of code with this PR:

run this block of code only when running with keycloak

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[saw-jan]

LGTM