Fix changeset checker to stop using since option

[hsubox76]

The option doesn't do what I thought it did, it should be calling the normal changeset status command. It just needs to explicitly pull master first so that the command doesn't fail.

--no-rebase avoids the warning message of not specifying a default merge strategy while selecting what would have been the default anyway.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c19a25d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[google-oss-bot]

Binary Size Report

Affected SDKs

No changes between base commit (49b0406) and head commit (4ad33d4).

Test Logs

• Base (49b0406a): https://github.com/firebase/firebase-js-sdk/actions/runs/1279462829
• Head (4ad33d4b): https://github.com/firebase/firebase-js-sdk/actions/runs/1280525899

[google-oss-bot]

Size Analysis Report

Affected Products

No changes between base commit (49b0406) and head commit (4ad33d4).

Test Logs

• Base (49b0406): https://github.com/firebase/firebase-js-sdk/actions/runs/1279462829
• Head (4ad33d4): https://github.com/firebase/firebase-js-sdk/actions/runs/1280525899