During the upgrade tests the seeding phase of the test uses a
randomised container name which is then used as hostname for the
instance config. Subsequently when we upgrade the instance, we reuse
the config, but spin up a new container which has a new name. This
causes the instance config to differ from actual hostname.

While today we don't observe any failures in our suite, this is solely
due to the minimal set of tests we are actively using in the suite.
When we try to run tests such as those that e.g. interact with WebIDE
we observe failures due to the hostname not matching the config.

In order to best replicate a realistic upgrade scenario we should keep
the container name consistent between runs.

Changelog: changed

Use consistent container name for each upgrade step

See merge request !1380

Merged-by: Tiffany Rea <trea@gitlab.com>
Approved-by: Ievgen Chernikov <ichernikov@gitlab.com>
Approved-by: Tiffany Rea <trea@gitlab.com>
Co-authored-by: John McDonnell <jmcdonnell@gitlab.com>

Changelog: removed

Temporarily Remove AI Gateway Logging

See merge request !1381

Merged-by: Dan Davison <ddavison@gitlab.com>
Approved-by: Dan Davison <ddavison@gitlab.com>
Co-authored-by: Valerie Burton <vburton@gitlab.com>

Bump version to 14.19.1

See merge request !1382

Merged-by: Mark Lapierre <mlapierre@gitlab.com>
Approved-by: Mark Lapierre <mlapierre@gitlab.com>
Co-authored-by: Valerie Burton <vburton@gitlab.com>