Co-authored-by: Gareth Thackeray <[email protected]>

* next:
  Do not trigger pipelines using async
  Ensure RN build steps fail if command is unsuccessful
  fix(test): lock `react-native-gesture-handler` in the RN test fixtures to version `2.62` to avoid kotlin version conflicts
  deps(react-native): Update bugsnag-cocoa to v6.24.0 (#1825)

* 'plat-8731' of github.com:bugsnag/bugsnag-js: (51 commits)
  deps(react-native): Update bugsnag-cocoa to v6.25.0
  Build legacy docker image
  Reinstate browser tests on Android 4
  Revert "Reinstate browser tests on Android 4"
  Reinstate browser tests on Android 4
  No need to wait for the android builder
  Remove responsibility for testing RN with latest native notifiers
  Split RN pipeline into iOS and Android parts
  Clear persistent data between E2E scenarios (#1848)
  Apply memory settings to all fixtures
  Increase memory
  Use Maze v7 for all RN CLI steps
  Relax test to allow more than 1 session to be sent
  v7.18.1
  update CHANGELOG.md
  Move expo trigger to the end
  Group for each pipeline
  Wait steps are ugly
  Correct dependency tree for regrouped browser jobs
  Can’t have nested groups
  ...

Trigger builds on all maintained Expo branches

Pin React Native Navigation for RN 0.66

Various RN test fixture build fixes

Bump bugsnag-android dependency to v5.28.2

Regenerate RN test fixture lock files

Bump bugsnag-android dependency to v5.28.3

Reinstate macOS Electron tests on Node 12

* next: (25 commits)
  dup: bump bugsnag-android dependency to v5.28.3
  Set environment variables as strings
  Debug
  Add tests on Node 12, using Buildkite build matrix
  Regenerate RN test fixture lock files
  dup: bump bugsnag-android dependency to v5.28.2
  Fix RN build
  Let NOTIFIER_VERSION in
  Remove Flipper
  RN build fix
  Update patch versions of RN test fixtures
  Remove remaining mentions of jcenter
  Pin React Native Navigation for RN 0.60
  Trigger all three Expo branches
  v7.18.2
  update CHANGELOG.md
  Remove Flipper
  Remove flipper
  Remove Flipper
  Add mavenCentral
  ...

* Update node maze-runner version to v7

* Update maze-runner version for running node locally, and fix missing-step typo

…lder node versions

Update browser delivery tests to respond with a log, add delivery tests to node

* next:
  Update node maze-runner version to v7 (#1871)

* 'plat-8731' of github.com:bugsnag/bugsnag-js: (22 commits)
  Use correct parse method
  Ensure the correct version of url is present
  Ensure the correct version of url is present
  Fix incorrect URL
  Crop even more out
  Remove potentially problematic big-data generation
  Remove problematic HTTP code
  Ensure logs uri is passed through to containers and use http lib in older node versions
  Update to Node V7 and add express oversized scenario
  Temporarily disable delivery test on node and on ie10
  Update to ensure errors are logged correctly
  Update node to maze-runner v7
  Add basic node log implementation and extra logs to ie10
  Attempt cross-platform xhr response
  Remove feedback from log and rely on signle response only
  Return the full err
  Return the event instead of err
  Use actual steps
  Log feedback inplementation
  Use the post response instead of options
  ...

This is getting stuck somewhere while running the tests, so I've
temporarily disabled the code coverage checks to allow the browser size
check to run

Remove code coverage from pr diff bot

The previous '_features' type definition means 'a FeatureFlag or an
array of nulls', but should be 'an array of FeatureFlags and/or nulls'

Fix parts of request metadata being missing from some events

Add unit tests for clone-client

This allows plugins to make changes to any new clones, which may be
necessary if they are monkey patching clients

clone-client doesn't copy over monkey patched methods on to new clones¹,
so we have to hook into the cloning process to monkey patch them

¹ This is actually a good thing as monkey patched methods will usually
work by holding a reference to an old client to call the un-patched
method. If we copied them over then they would still reference the
original client, not the clone

This means we don't need to bump this manually every time (though we
still should to make sure the other versions are up-to-date)

🔵

Fix in-flight being unable to track event requests made by cloned clients

Bump browser versions

Update @bugsnag/expo versions in the pipeline

When a server plugin (e.g. Express) is loaded, we need to clone the
client returned from `startSession` in order for them to behave as
expected

We can't unconditionally clone clients as this causes events and
sessions to be associated with different clients, breaking the link
between the two

Update RN pipeline to use Maze Runner v7