[db] Create d_b_personal_access_token

[laushinka]

Description

Creates d_b_personal_access_token with the following schema

--	field	type
primary key	id	varchar
idx	user_id	varchar
idx	hash	varchar
	name	varchar
	description	text
	scopes	text
	expiration_time	timestamp
	created_at	timestamp
idx	last_modified	timestamp
	deleted	boolean

Related Issue(s)

Part of #14602

How to test

Build

Release Notes

NONE

Documentation

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-lau-db-tokens.4 because the annotations in the pull request description changed
(with .werft/ from main)

[laushinka]

/werft run

👍 started the job as gitpod-build-lau-db-tokens.5
(with .werft/ from main)

[easyCZ]

/werft run

👍 started the job as gitpod-build-lau-db-tokens.6
(with .werft/ from main)

[easyCZ]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-lau-db-tokens.7
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-lau-db-tokens.8 because the annotations in the pull request description changed
(with .werft/ from main)

[laushinka]

Build succeeds without preview. Let me try again with preview.

[werft-gitpod-dev-com]

started the job as gitpod-build-lau-db-tokens.9 because the annotations in the pull request description changed
(with .werft/ from main)

[laushinka]

This fails consistently with preview, even when triggered manually from a workspace.
Running again from here without preview, to get the build green.

/werft run

👍 started the job as gitpod-build-lau-db-tokens.11
(with .werft/ from main)

Update: Aaand it failed again

[laushinka]

Closing this because of flaky builds. New PR here.