Enhance cost estimator

[pburkholder]

I love the new cost estimator on the pricing page. A few ideas to make it more useful

Notes

• The quantity field should accommodate 5 digit numbers, since someone could have 10,000 GB of S3 data.
• Add a documentation link to each service once you've added it.

 {
      "name": "External Domain",
      "documentation": "https://docs.cloud.gov/platform/services/external-domain-service",
      "plans": [
        {
          "plan": "domain-with-cdn-dedicated-waf",
          "credits": 1
        }
      ]
    }

• Provide a Tier estimate, e.g.:

• Include more of the free services
• Re-order the services (Start with app memory, then S3, then RDS, remaining AWS services, then external domain, etc)
• Download a CSV (optional, let's discuss)

Acceptance Criteria

• Determine next steps and acceptance criteria

[sknep]

These are great ideas!!! I don't mind if you have someone else work on it with you while I'm gone. Maybe @zjrgov or @markdboyd? they've shown related interest in the past. Otherwise I'll see what's on my plate when I'm back from vacation.

Keep in mind that the code powers both the regular estimator and the workshop planner, so changes will affect both. We can separate them if their experiences need to diverge.

[mogul]

The way I'd like to use this is

1. spec out what I think I'll need in a specific environment I call "production"
2. clone "prod" environment to one called "staging"
3. reduce the plans, quantities, and sizes in "staging"
4. clone "staging" environment to one called "dev"
5. further reduce the plans, quantities, and sizes in "dev"
6. add any dev-only resources (eg IDP service)
7. clone "dev" as many times as needed
8. see the total estimated credits and minimum tier that includes that many, as in Peter's screenshot

Then I have a quote I can come talk to you about, and also an idea of what it will cost in practice to wave at my boss.