chore: fix go.work file and run make format

[Pantani]

No description provided.

[julienrbrt]

The go.work and go.work.sum shouldn't be committed.

[jeronimoalbi]

Why do we want to commit go.work instead of go.work.example?

[Pantani]

@jeronimoalbi , @julienrbrt . We agree to not commit the go.work.sum. But why do we not commit to go.work?

And why keep the go.work.example if we are not using it?

[julienrbrt]

@jeronimoalbi , @julienrbrt . We agree to not commit the go.work.sum. But why do we not commit to go.work?

And why keep the go.work.example if we are not using it?

go.work makes it easy for local development but it's going to make unclear what versions uses a program when tagging it (as the tagged version should depend on tagged version - like you should not tag something that depends on local replaces)

Keeping a go.work.example is handy for anyone using go.work, but when they submit a PR to the repo they need to make sure they only use released version, or split the PR.

There's a lengthy discussion about this in the SDK somewhere.

[Ehsan-saradar]

Yep, @julienrbrt is right. This is also the case with ibc-go repository.