refactor: simply errors

[julienrbrt]

Description

As Facu rightfully pointed, the SDK uses 5 packages for errors:

• errors (stdlib)
• cosmossdk.io/errors
• github.com/cosmos/cosmos-sdk/types/errors
• github.com/pkg/errors
• github.com/cockroachdb/errors

This PR attempts to simplify this by:

• removing the alias to cosmossdk.io/errors from github.com/cosmos/cosmos-sdk/types/errors (refactor: fix lint issues + gofumpt #15062 (comment))
• remove the usage of github.com/pkg/errors, except in cosmossdk.io/errors, until we migrate to cockroachdb/errors there too.
• got some errors due to log version, this should be fixed after feat!: use cosmossdk.io/log logger #15011, but went ahead and updated to a pseudo version for now

---

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)

[julienrbrt]

This was broken, as there were no import for errorsmod.
Checking if CI checks the errors package properly.

[tac0turtle]

left one comment, its a bit hidden how errors and pkg/errors .new work. Its quite annoying. If we are fine with not having stack traces on every error this is chill

[alexanderbez]

Thanks @julienrbrt 🙏