Add Google Calendar env keys for canonical-com-blog

[nathanclairmonte]

Done

• Added SERVICE_ACCOUNT_EMAIL and SERVICE_ACCOUNT_PRIVATE_KEY env variables to the /blog route in site.yaml, for both production and staging, as this was stopping deployments from succeeding.

QA

• Check out this feature branch
• Run the site using the command dotrun
• View the site locally in your web browser at: http://0.0.0.0:8002/

[webteam-app]

Demo starting at https://canonical-com-1215.demos.haus

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.14%. Comparing base (49c790a) to head (279d611). Report is 4 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1215 +/- ## ========================================== - Coverage 71.45% 66.14% -5.31% ========================================== Files 12 10 -2 Lines 1023 898 -125 ========================================== - Hits 731 594 -137 - Misses 292 304 +12 ``` | [Flag](https://app.codecov.io/gh/canonical/canonical.com/pull/1215/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical) | Coverage Δ | | |---|---|---| | [python](https://app.codecov.io/gh/canonical/canonical.com/pull/1215/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical) | `66.14% <ø> (-5.31%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=canonical#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.