2677 - Add sendgrid api key to deploy-backend

[jtimpe]

Summary of Changes

Pull request closes #2677

How to Test

1. In the TDRS Project Settings in circleci, add a new Environment Variable: SENDGRID_API_KEY (or verify/modify the existing value). If you change it, you'll be able to see the change in the final step
2. Trigger a circleci deployment to a cloud.gov environment of your choice
3. In the tdrs-backend-{env} environment variables in cloud.gov, verify the value from circleci is in place for SENDGRID_API_KEY

Proof from my test

Deliverables

More details on how deliverables herein are assessed included here.

Deliverable 1: Accepted Features

Checklist of ACs:

• add SENDGRID_API_KEY to deploy-backend.sh to be managed by circleci
• document that all environment variables should be managed by circleci
• lfrohlich and/or adpennington confirmed that ACs are met.

Deliverable 2: Tested Code

• Are all areas of code introduced in this PR meaningfully tested?
  • If this PR introduces backend code changes, are they meaningfully tested?
  • If this PR introduces frontend code changes, are they meaningfully tested?
• Are code coverage minimums met?
  • Frontend coverage: [insert coverage %] (see CodeCov Report comment in PR)
  • Backend coverage: [insert coverage %] (see CodeCov Report comment in PR)

Deliverable 3: Properly Styled Code

• Are backend code style checks passing on CircleCI?
• Are frontend code style checks passing on CircleCI?
• Are code maintainability principles being followed?

Deliverable 4: Accessible

• Does this PR complete the epic?
• Are links included to any other gov-approved PRs associated with epic?
• Does PR include documentation for Raft's a11y review?
• Did automated and manual testing with iamjolly and ttran-hub using Accessibility Insights reveal any errors introduced in this PR?

Deliverable 5: Deployed

• Was the code successfully deployed via automated CircleCI process to development on Cloud.gov?

Deliverable 6: Documented

• Does this PR provide background for why coding decisions were made?
• If this PR introduces backend code, is that code easy to understand and sufficiently documented, both inline and overall?
• If this PR introduces frontend code, is that code easy to understand and sufficiently documented, both inline and overall?
• If this PR introduces dependencies, are their licenses documented?
• Can reviewer explain and take ownership of these elements presented in this code review?

Deliverable 7: Secure

• Does the OWASP Scan pass on CircleCI?
• Do manual code review and manual testing detect any new security issues?
• If new issues detected, is investigation and/or remediation plan documented?

Deliverable 8: User Research

Research product(s) clearly articulate(s):

• the purpose of the research
• methods used to conduct the research
• who participated in the research
• what was tested and how
• impact of research on TDP
• (if applicable) final design mockups produced for TDP development

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.96%. Comparing base (01c4117) to head (1693205).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3019      +/-   ##
===========================================
- Coverage    93.11%   92.96%   -0.15%     
===========================================
  Files          273      276       +3     
  Lines         7087     7140      +53     
  Branches       598      603       +5     
===========================================
+ Hits          6599     6638      +39     
- Misses         395      407      +12     
- Partials        93       95       +2     

Flag	Coverage Δ
dev-backend	93.02% <ø> (-0.17%)	⬇️
dev-frontend	92.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 52aa35f...1693205. Read the comment docs.

[elipe17]

Checked CirCI and the Raft env and verified the var was there.

[raftmsohani]

LGTM!

[ADPennington]

backend before deployment

backend after deployment

email sent ✔️