task(customs): Alter customs rules for getCredentialStatus action

[dschom]

Because

• We've seen an increase in 'unblock sign in' page views, which led to investigating the customs config.
• If a key stretching upgrade occurs, we will trigger a getCredentialsStatus, passwordChange & accountLogin action.
• Therefore we potentially have 3x the number actions during an upgrade scenario.

This pull request

• Moves the getCredentialStatus action into the ACCOUNT_STATUS_ACTION set, which more correctly fits the nature of this action.
• The default for maxAccountStatusCheck has been increased, because key stretching changes need a bit more overhead for these types of actions.

Issue that this pull request solves

Closes: FXA-10777

Checklist

Put an x in the boxes that apply

• [x] My commit is GPG signed.
• [ ] If applicable, I have modified or added tests which pass locally.
• [ ] I have added necessary documentation (if appropriate).
• [ ] I have verified that my changes render correctly in RTL (if appropriate).

Screenshots (Optional)

Please attach the screenshots of the changes made in case of change in user interface.

Other information (Optional)

Any other information that is important to this pull request.