feat: allow breaking changes, immediate sunset of experimental

Experimental versions may be sunset without notice.

Breaking changes are allowed in experimental versions without notice.

chore: update & improve e2e tests

With experimental allowing breaking changes, we need better e2e test
coverage for breaking changes in stability levels that allow/deny them.

In updating these, several problems were identified and fixed in e2e
tests:
- gaps in coverage for bulk post
- yarn cruft in output
- non-obvious asserts, replaced with cleaner bash functions

chore: more unit test coverage for breaking changes

.circleci/config.yml

@@ -28,8 +28,11 @@ jobs:
           name: Test
           command: yarn test
       - run:
-          name: E2E Test
+          name: E2E Test - Bulk Compare
           command: ./end-end-tests/api-standards/test-bulk.bash
+      - run:
+          name: E2E Test - Compare
+          command: ./end-end-tests/api-standards/test.bash
 
   npm-release:
     <<: *defaults

end-end-tests/api-standards/context-beta.json

@@ -0,0 +1,9 @@
+{
+  "changeDate": "2021-11-11",
+  "changeResource": "thing",
+  "changeVersion": {
+    "date": "2021-11-10",
+    "stability": "beta"
+  },
+  "resourceVersionReleases": {}
+}