add env vars to the charm deployment

[jmuzina]

Done

• Add charm environment variables needed for external API calls (GitHub API, Google Search API)
• Upgrades to flask-base 2.6.0 per recommendation by @samhotep - it loads FLASK_-prefixed env vars for us. Add flask secret key canonicalwebteam.flask-base#87
• Configures gunicorn to avoid timing out on requests to external APIs by increasing timeout threshold and adding an additional worker
• Minor documentation tweak for how to authenticate / create the charmhub token

QA

• Go to staging.vanillaframework.io (currently already deployed to PS6 with this charm).
• Open the search bar, and enter any search query. See that the search is submitted and does not throw a 500 error. Ex: test query
• Go to the contributors page and verify it does not throw a 500 error (displays contributors list)

Check if PR is ready for release

If this PR contains Vanilla SCSS or macro code changes, it should contain the following changes to make sure it's ready for the release:

• PR should have one of the following labels to automatically categorise it in release notes:
  • Feature 🎁, Breaking Change 💣, Bug 🐛, Documentation 📝, Maintenance 🔨.
• Vanilla version in package.json should be updated relative to the most recent release, following semver convention
  • if existing APIs (CSS classes & macro APIs) are not changed it can be a bugfix release (x.x.X)
  • if existing APIs (CSS classes & macro APIs) are changed/added/removed it should be a minor version (x.X.0)
  • see the wiki for more details
• Any changes to component class names (new patterns, variants, removed or added features) or macros should be listed on the what's new page.

[webteam-app]

Demo

Jenkins

demos.haus

[advl]

why the version pinning ?

[jmuzina]

You're looking at an old version here, that pin was used for a bit in this PR while I was debugging some things, but it's been removed now.