feat(compass-global-writes): sharding error state COMPASS-8349

[paula-stacho]

Description

Notes:

• the CreateShardKeyForm is simply moved out of unsharded state, as it is now reused for both Unsharded and ShardingError states - changes pointed out in a comment
• the ShardingError also displays the error and a button to cancel sharding. this means that from this state the user can either go back (via the cancel button), or forward (by submitting the form)
• again, the implementation is based on mms. for example:
  • the error parsing https://github.com/10gen/mms/blob/fdad01af9558be4f9e940e0aaa50d5a3a1f0c6cf/client/packages/common/utils/deploymentStatusError.ts#L26
  • the banner being a warning level 🤷 (these levels are one of the things I want to check with design) https://github.com/10gen/mms/blob/74cf2c73b098b977cfbed907c1990b13a11b93c5/client/packages/project/metrics/components/DataExplorerShardKey.tsx#L903

I have thought about whether this state needs to be separate, or if it would better be the unsharded state with optional error. In the end I continued the approach with separate states and the store behaving as a state machine. It still makes sense to me and I find it better than having a ton of conditional bits in the components. But, I've been working on this for a while, so I'm definitely biased and I wouldn't be surprised if the solution isn't that clear to someone else - let me know if that's the case and we can talk about how to make it clearer!

Preview:
if you happen to read the error message - this one actually should be handled in a different way (key mismatch screen), but this was the easiest for me to reproduce

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[paula-stacho]

Small change here. It used to be:

disabled={!secondShardKey || isSubmittingForSharding}
variant="primary"
leftGlyph={
  isSubmittingForSharding ? (
    <SpinLoader title="Creating shard key" />
  ) : undefined
}

[paula-stacho]

Another small change - this is now connected directly, and it works with error/no error statuses.

[mabaasit]

this adds extra space in the banner and the message looks a bit weird (in the screenshot attached in the PR description). also, would be nice if we can split the error message by new line (server error has it).

[paula-stacho]

changed this setting for the error specifically. otherwise most messages I tried looked better with justify. also added pre-wrap on the error.