Trigger variables column from Pipeline trigger is not scrollable

Summary

When a pipeline starts by Pipeline trigger using the variables provided along with the trigger commands. The variables are put into the trigger variables column in the right panel which is not scrollable or adjustable.

If there's any long key name, it will push the value field out of the field of view so there's no way to see the value for each key. The user would need to copy the table and paste it somewhere else as a workaround.

Steps to reproduce

1. Setup a pipeline trigger for a project
2. Use the triggger curl --request POST \ --form token=TOKEN \ --form ref=master \ --form "variables[SOME_LONG_VARIABLE_KEY]=randomvaluehere" \ "https://gitlab.example.com/api/v4/projects/9/trigger/pipeline" to trigger a pipeline with variables
3. Go to the job and view the right panel, see that only the trigger variable key column is visible and we cannot scroll to see the variable value.

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com; GitLab Enterprise Edition 13.11.0-pre 05a6be0c

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes