Support sites with custom environment types

[sejas]

Related issues

• Fixes STU-641

Proposed Changes

• Accept any Environment type from the API. Restriction added on https://github.com/Automattic/studio/pull/1512/files#diff-58affd73bc0179c3ce9580202613b0d58adc82ac2ad4d57ae542337292f3617fR18
• Moves sync files related to environment badges into the modules/sync folder
• It doesn't change how the badges are displayed. The current behaviour is WPcom displays staging production based on the isStaging prop, and it doesn't display the environment_type returned by the site. Pressable sites can display any environment_type.

Testing Instructions

• Modify your production WPcom's environment_type to development in network admin settings tab.
• Run npm start
• Observe your site appears in Studio
• Open the sync modal
• Observe the environment
• Connect the site
• Open the pull and push dialogs.
• Observe the texts remain the same as before.

Before this PR the site wouldn't appear.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[gcsecsey]

Thanks @sejas for fixing showing sites with custom environment types. The changes make sense to me, and work great, now I'm able to add my site with a custom type and pull/push to it.

I set my site's environment_type to testing:

When connecting a site, the site is no longer filtered out in the site list:

trunk	this branch

The pull and push dialogs still display "Production" on the badge:

Pull	Push