In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

As we are constantly upgrading Flagr server, the client SDKs may experience unexpected changes from the server side. The integration tests should better include these SDKs instead of just simple CURL tests.

Specifically, we want to cover

• https://github.com/checkr/jsflagr
• https://github.com/checkr/rbflagr
• https://github.com/checkr/pyflagr
• https://github.com/checkr/goflagr

Would be great to have a few more concrete examples, especially examples with namespaces.

Would also be cool to have a simple interactive app that generates the jsx for a particular experiment definition

cc @mattrheault

https://github.com/HubSpot/PlanOut.js/blob/master/es6/experiment.js#L32

Ideally we should have a way to proxy params when they are set so that the names exist on the experiment class instance.

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

1. Add sample size estimation documentation.
2. Improve multiple correction documentation adding all formulas and assumptions.

feel free to add more

Documentation is not up to date

For example, supported datastores misses PGSQL
https://maif.github.io/izanami/manual/architecture/index.html

Please documentation freshness problems in this issue

Are there additional docs anywhere that contain recipes/examples of how to set up both the "redirect to page" type A/B testing, as well as the "triggered by JS" version of A/B testing?

For example, rather than "real" pages, we're looking to do A/B testing on an in-model subroute using the RoutablePageMixin, and it would be