Colin Egress release ticket 30.2

Tickets for release - Test June 1st, Prod June 4th
Prior to moving into production, the following steps should be completed or confirmed:
- [ ] Add release # to this ticket
- [ ] Create a Release Report: [Report](https://app.zenhub.com/workspaces/colin-egress-team-6904d552be2bb0000fa13ad6/reports/release?release=Z2lkOi8vcmFwdG9yL1JlbGVhc2UvMTE0OTkw)
- Update version numbers in the code being released and list them here:
- [ ] Business API: v3.1.3
- [ ] PPR API: 1.3.18

- [ ] Create a draft releases in GitHub:
1. Confirm the correct commits are present
2. Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a
reference to a branch
3. Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
- [ ] Ensure that the commit list is represented on the Release Report
1. tag all respective tickets to current release
- [ ] Ensure deployment steps are filled in - remove/replace placeholders
- [ ] Post message that projects are being deployed to Test in "Colin Egress Team" channel
- [ ] Deploy the code to Test (STEPS BELOW) _Completed by entities_

### Deployment Steps

#### Dev:
- [ ] Business API: v3.1.3
- [ ] PPR API: 1.3.18

#### Test:
- [ ] Business API: v3.1.3
- [ ] PPR API: 1.3.18

### Smoke Test Script

- [ ] watch logs in GCP for 60 minutes (https://console.cloud.google.com/logs/)

Start with the linked release report and confirm the Business API v3.1.3 and PPR API 1.3.18 targets. Review the draft GitHub release, deployment steps, Test deployment checklist, and GCP smoke-test logs. Done means the release report, commit list, deployment details, notifications, deployments, and 60-minute log watch are all confirmed.

Written by the indexing model from the issue text.