Update Pact Broker URL

Our Pact Broker instance is being migrated from PaaS to Heroku.

data/repos.yml

@@ -690,8 +690,8 @@
 
 - repo_name: govuk-pact-broker
   team: "#govuk-platform-security-reliability-team"
-  production_url: https://pact-broker.cloudapps.digital/
-  production_hosted_on: paas
+  production_url: https://govuk-pact-broker-6991351eca05.herokuapp.com/
+  production_hosted_on: heroku
   type: Utilities
   sentry_url: false
   dashboard_url: false

source/manual/pact-testing.html.md

@@ -17,7 +17,7 @@ Since in tests we do not want to spin up both apps to test the interactions, pac
 For example, the Imminence API has a "pact" or "contract" with GDS API Adapters:
 
 - the expected interactions are defined in [imminence_api_pact_test.rb in GDS API Adapters](https://github.com/alphagov/gds-api-adapters/blob/main/test/pacts/imminence_api_pact_test.rb)
-- when these tests are run they output a JSON pactfile which is published to [our pact broker](https://github.com/alphagov/govuk-pact-broker) ([live site](https://pact-broker.cloudapps.digital/))
+- when these tests are run they output a JSON pactfile which is published to [our pact broker](https://github.com/alphagov/govuk-pact-broker) ([live site](https://govuk-pact-broker-6991351eca05.herokuapp.com/))
 - the build of Imminence will setup a [test environment](https://github.com/alphagov/imminence/blob/9a4801da9d58be0af886d9095328894aac56917c/spec/service_consumers/pact_helper.rb) and use this pactfile to test the real API
 
 GDS API Adapters is really a proxy for real "consumer" apps, like Whitehall. The gem includes [a set of shared stubs](https://github.com/alphagov/gds-api-adapters/tree/master/lib/gds_api/test_helpers) for use in each app's own tests ([example](https://github.com/alphagov/contacts-admin/blob/e935fa54bf71c0063bb92faeaf8a27d1618e00ee/spec/interactors/admin/clone_contact_spec.rb#L11)). Using the stubs ensures each app stays in sync with GDS API Adapters, which can then do contract testing on their behalf.