Breaking changes flow

[S2Ler]

• Uses swift package diagnose-api-breaking-changes to detect breaking changes.
• I wasn't able to setup mbx-ci/gh tools to post pr comments, so if job fails, you will have to go to circleci and check what's wrong. The list of breaking changes will be available in artificats.

[bamx23]

We should also add a new step to releasing instructions:

After releasing a final or RC version, update swift-package-baseline/baseline.txt, run swift package diagnose-api-breaking-changes --products MapboxDirections --baseline-dir swift-package-baseline --breakage-allowlist-path swift-package-baseline/breakage-allowlist-path.txt $(cat swift-package-baseline/baseline.txt) and remove previous baseline directory(the one with commit hash).

We can also automate this as part of the release process on CI by creating a pipeline that runs this on tag push and creates a PR.

[S2Ler]

We can also automate this as part of the release process on CI by creating a pipeline that runs this on tag push and creates a PR.

As I mentioned in the previous step it is not designed to be updated frequently. The script is added though. CI integration isn't important enough given that you don't need to run it frequently. But can be done in a separate PR if needed.

[bamx23]

Looks good, just several suggestions.
And it's only 2-3 minutes to run this new CI job without a cached/vendored baseline, nice!