style: Use require.ErrorIs whenever possible

[alarso16]

Why this should be merged

Works to follow avalanchego's linter whenever possible. Some of the ErrorContains really tested geth code, making it difficult to remove.

How this works

Uses sentinel errors and nolint clauses.

How this was tested

Existing UT

Need to be documented?

No

Need to update RELEASES.md?

No

[JonathanOppenheimer]

Just a question (and I'll do an actual review) - I remember talking about the vmerrorsin terms of the uplift - do we want to use that package for the sentinel errors declared? Do we want to get rid of the package entirely?

[alarso16]

Just a question (and I'll do an actual review) - I remember talking about the vmerrorsin terms of the uplift - do we want to use that package for the sentinel errors declared? Do we want to get rid of the package entirely?

That package is used to share errors between packages to avoid circular dependencies - for the errors I added, I didn't actually need to move them, but I definitely could. I think the package is necessary for the existing errors though

[JonathanOppenheimer]

Just a question (and I'll do an actual review) - I remember talking about the vmerrorsin terms of the uplift - do we want to use that package for the sentinel errors declared? Do we want to get rid of the package entirely?

That package is used to share errors between packages to avoid circular dependencies - for the errors I added, I didn't actually need to move them, but I definitely could. I think the package is necessary for the existing errors though

I see - I didn't realize it was just for errors that would create circular dependencies!

[JonathanOppenheimer]

By the way the vmwrrors package should be can be removed entirely -- obviously not for this PR but if you take a look at my uplift PR Josh explained how.