need #7217 merged first

I had to merge some arrays so it got more complicated :/

I WILL BRING ORDER TO THIS AAAAHHH

I'm honestly not sure why i lost the deterministic ordering of the fields of all the generated code but now its nice and sorted.

bip340sig is now String type in rust and .proto, same as signature

We derived the i32 from rust enums implicitly by their order in the enum. I added explicit numbers in #7217 so the sorting doesn't mess anything up.

Btw if we ever delete an "open" enum field in *.proto with 0 it's going to be trouble. They must start with a field that is 0. But that's for a future PR.

Btw if we ever delete an "open" enum field in *.proto with 0 it's going to be trouble. They must start with a field that is 0. But that's for a future PR.

We might want to keep dummy placeholders in there once we do. But we'll cross that bridge once we get to it.

I don't fully understand why sorting is required here, does it have to do with the iteration through nested fields? Otherwise it feels strange to have enums not be in numeric order, but no real issue, I'm just curious :-)

Yes when merging the arrays that were previously not collected we would get enums in node.proto that were out of order. And protoc wants them to start at 0. The ordering of enums in the rust files could be removed eagain after the explicit enum values were added. I don't remember exactly why i sorted those to be honest. Want me to check that out?

rebased and rust model enums sorted by number not name

Rebased on top of master after merging #7217, and merging as soon as it passes CI (the previous CI failure was a flake).

i have a bunch more coming but i wait until this and #7230 is merged