Pin Version of google-chrome-stable Package

[Hamms]

Right now, we have a couple different versions of this package installed across our servers. Checking with apt-cache policy google-chrome-stable reveals:

staging:
google-chrome-stable:
  Installed: 103.0.5060.53-1
  Candidate: 113.0.5672.126-1
  Version table:
     113.0.5672.126-1 500
        500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
 *** 103.0.5060.53-1 100
        100 /var/lib/dpkg/status

test:
google-chrome-stable:
  Installed: 77.0.3865.90-1
  Candidate: 103.0.5060.53-1
  Version table:
     103.0.5060.53-1 500
        500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
 *** 77.0.3865.90-1 100
        100 /var/lib/dpkg/status

The discrepancy between staging and test specifically is causing some problems; some apps code using newer browser features fails to build on test but passes on staging, which can lead to confusingly delayed DTT failures when staging builds the apps package at first and test only attempts to build some time after the offending PR has been merged.

To resolve, we explicitly specify which version we should target. I've chosen to target the version currently installed on staging because it's closest to the version we target for our UI tests, but we could alternatively choose to update to version 113.

Links

See threads at https://codedotorg.slack.com/archives/C0T0PNR0D/p1683573120446859 and https://codedotorg.slack.com/archives/C0T0PNTM3/p1684359034466229and for more context.

Testing story

Verified on an adhoc that we correctly install the targeted version.