Update configuration for dev/test/prod values

#### Description:

See: https://github.com/bcgov/reserve-rec-api/blob/main/template.yaml#L701-L703

We need to adjust these values to be more appropriate for dev/test/prod.

#### Acceptance Criteria:
Parameterize the github action and sam template to reference dev/test/prod secrets in github environment vars.

#### Development Checklist:

- [ ] parameterize the github action
- [ ] set the values appropriately in github environments

#### Dependencies

- Blocked by
- Blocking

**Relevant documentation as reference**

**Definition of Ready**

- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if applicable)
- [ ] Design / Solution is accepted by Product Owner (if applicable)
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

**Definition of Done**
- In progress:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] UI meets accessibility requirements
- [ ] Unit tests are written
- [ ] Work is traceable in GitHub
- [ ] PR linked to ticket number
- [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
- Code review:
- [ ] Code is peer reviewed and has passed CI/CD tests
- QA:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Code is potentially shippable to the production environment
- [ ] Functional features have been tested and passed by QA
- [ ] UI components tested by designer
- [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
- PO Review:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Reviewed and approved by Product Owner

#### Notes:
-
-

Start with template.yaml lines 701-703 and the repository's GitHub Actions workflow. Trace how SAM parameters and GitHub environment secrets are currently supplied; done means dev, test, and prod environments reference their appropriate secrets and the action and template are parameterized.

Written by the indexing model from the issue text.