feat(types/errors)!: update to latest errors module beta

[aaronc]

Description

Follow-up to #11274

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[aaronc]

Why so many unrelated test failures??

[aaronc]

Any idea what's happening here anyone? I can't imagine these CI failures are due to this PR and things passed when I tested locally

[amaury1093]

I see failing tests in group, it might be related to #11168. We can assign someone to have a look there

[aaronc]

I see failing tests in group, it might be related to #11168. We can assign someone to have a look there

In that case should we consider this safe to merge?

[amaury1093]

In that case should we consider this safe to merge?

Merging this now would prevent automerge doing its work on all other PRs. I would advise waiting for #11168, @atheeshp is looking into it

[atheeshp]

In that case should we consider this safe to merge?

Merging this now would prevent automerge doing its work on all other PRs. I would advise waiting for #11168, @atheeshp is looking into it

FYI, @aleem1314 opened a draft PR(#11338) for #11168, and he would like to continue on it.

[aaronc]

@AmauryM there are legitimate errors related to the group module here. I'm not sure if it's just the test that needs to be updated or the code. The test is expecting a different error than the one it got