Add error state to nimble-checkbox

[mollykreis]

Pull Request

🤨 Rationale

This is part of #2018 and also resolves #2091

👩‍💻 Implementation

The nimble-checkbox now implements ErrorPattern to add error-text and error-visible to its API.

The bulk of the implementation is updating the template and styles of the checkbox. These changes include:

• Adding error icon/text to the template with appropriate styles
• Fix the wrapping behavior to keep the checkbox aligned with the top line of text rather than centered within the control
• Update the checkbox to have a default min-height of controlHeight (see nimble-checkbox has incorrect height #2091)

🧪 Testing

• Existing unit tests pass
• Manually tested in storybook
• Extended matrix tests to cover more cases -- error states and wrapping text

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.

[mollykreis]

This isn't a required change as part of this PR, but I noticed that slot[name='checked-indicator'] svg was listed twice in the styles, so I combined them.

[mollykreis]

@msmithNI, will you buddy this PR for me?

[jattasNI]

Am I correct that the styling changes will impact clients by adding additional space around their checkboxes? For example, in the example app it looks like the checkbox has some extra space on all sides so no longer left aligns with the label above it.
https://60e89457a987cf003efc0a5b-ndvckxqkhv.chromatic.com/example-client-app/#/customapp
https://nimble.ni.dev/storybook/example-client-app/#/customapp

Is that an intentional design change? If so then I think we should:

1. mention it in the change file comment
2. spot check a few SLE apps to ensure it looks ok (I think Fred has complained that a lot of slide outs already have bad checkbox layouts so maybe this is a low bar)

I don't think it merits being marked as a breaking change or doing additional notifications on Teams, but we could consider those too if it seems disruptive.

[rajsite]

That padding inside the control bounds doesn't seem right. All our other controls are flush to the bounds of the control

[mollykreis]

The padding is coming from the visual design specs. Perhaps we need to have a discussion with Brandon if we don't agree with the design.

[rajsite]

I think either way I'd vote to split it out into a separate PR and not make the change here. If we do end up wanting it, I'd argue implementation-wise for the checkbox (which is a standalone control) that the padding / margin would be responsibility of the thing that is laying it out.

The padding is for a grouped, labelled set of checkboxes, not for every possible composition of a checkbox. We'd have a separate PR to capture the layout guidance in storybook docs or create something like a checkbox-group to help layout and we would also want to update radio button group at the same time.

[mollykreis]

I'll pull that change out of this PR.

[mollykreis]

The left padding has now been removed from the checkbox. The square control is back to being flush with the left edge of the nimble-checkbox.