btcec: update gomod and go version

[yyforyongyu]

TODO:

• tag btcec/v2.3.5
• tag btcutil/psbt/v1.1.10
• tag btcutil/v1.1.7

[guggero]

I think we might need to keep this at an older version? Or at least have the old 2-part format, since this seems to break the unit tests (or the linter).

[yyforyongyu]

i think there's something wrong with our CI here, still digging but the tests are failing locally but not on github actions hmmm

[yyforyongyu]

turns out that locally all the sub-modules are pointed to the local versions as indicated by the go.work, which is now fixed once the versions are updated here.

[Roasbeef]

Hmm, I do know there's this hardware wallet (?) that relies on GopherJS (Go transpiler) which doesn't support the latest version. In the past, we wanted to introduce some code using generics, but backed off at their request. Though ultimately we can't hold it all back forever...

[yyforyongyu]

hmm yeah didn't know that before. It looks like they only support up to 0.19.0, should we use 0.19.0 instead?

[coveralls]

Pull Request Test Coverage Report for Build 10484833064

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 12 unchanged lines in 4 files lost coverage.
• Overall coverage decreased (-2.0%) to 55.262%

---

Files with Coverage Reduction	New Missed Lines	%
btcutil/gcs/gcs.go	1	80.95%
mempool/mempool.go	1	66.67%
database/ffldb/db.go	5	91.23%
peer/peer.go	5	73.49%

Totals
Change from base Build 10411760109:	-2.0%
Covered Lines:	29835
Relevant Lines:	53988

---

💛 - Coveralls

[davecgh]

I no longer maintain this, so it's not my call, but I would highly suggest avoiding an entire dependency (and all of its dependencies, transitively) that everyone who uses the btcec module then has to also pull all for a single test.

I'm talking about testify here. Adding an entire dependency for a single test is kind of ridiculous.

[davecgh]

Also, requiring Go 1.22 when it doesn't actually require it is bad for consumers of the dependency too.