added form 10-7959a pagerduty service to settings.yml

[michaelclement]

Summary

This PR adds the Pager Duty service ID for the newly created Production: External: 10-7959a form service in Pager Duty. This is so we can schedule maintenance windows/downtimes for the form application.

Related issue(s)

• Pagerduty: Create a service for 10-7959a va.gov-team#102216
• 102216 - Add new pagerduty service dependency - form 10-7959a vets-website#35008

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• If this work is behind a flipper:
  • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
  • What is the testing plan for rolling out the feature?

Screenshots

NA

What areas of the site does it impact?

IVC forms 10-7959a

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[stevelong00]

Looks good!