Deploy to development on pushes to main

[atvaccaro]

Description

Closes https://github.com/cal-itp/reports/issues/176 Fixes https://github.com/cal-itp/reports/issues/115

I've updated the top-level repo README to include a description of the new deploys. I've left auto-deploys enabled in Netlify, but they won't trigger unless we push commits to the production branch.

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature
• [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Documentation

How has this been tested?

See development branch Actions.

Screenshots (optional)

[atvaccaro]

Can you add a little more clarification to the PR body about why this is being done incrementally / what the next steps are? One of the specific ACs in #176 is documentation of how this works, I understand if that is planned for later but I am nervous about making changes here without clarifying when that documentation will be ready/when the full workflow will be actually ready.

Related: Have the settings been changed on the Netlify side?

Basically just wondering if this PR will leave it in a state where it's impossible to deploy to prod?

I've added to the README, and I did leave Netlify continuous deploys enabled if we want to revert the CI/CD changes.