Run pipenv lock against all Pipfiles in repo

[adrianclay]

Why

This updates dependencies we have installed, fixing available security issues and bugs.

There are two Pipfiles which couldn't be updated:

• pipeline/scripts/setup-ec2-opentest/
• examples/supplier-example/

There were 228 security issues identified by Dependabot before merging this PR, and 147 after.

Script to recreate what we did

#!/bin/bash

piplock () {
  cd $(dirname $1)
  pipenv lock
  cd -
}

piplock integration-tests/fake_spine/Pipfile.lock
piplock integration-tests/fake_spineroutelookup/Pipfile.lock
piplock integration-tests/integration_tests/Pipfile.lock
piplock common/Pipfile.lock
piplock examples/SCR/Pipfile.lock
piplock examples/SCRWebService/Pipfile.lock
piplock mhs/common/Pipfile.lock
piplock mhs/inbound/Pipfile.lock
piplock mhs/outbound/Pipfile.lock
piplock mhs/spineroutelookup/Pipfile.lock
piplock pipeline/scripts/check-target-group-health/Pipfile.lock

# piplock pipeline/scripts/setup-ec2-opentest/Pipfile.lock Errored about 'NoneType' object has no attribute 'url'
# piplock examples/supplier-example/Pipfile.lock Errored about unable to find ./../../SCR

Type of change

Internal change (non-breaking change with no effect on the functionality affecting end users)

Checklist:

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users