Programmatically track version number for web3_clientVersion

[njgheorghita]

Automatically update trin version in web3_clientVersion response

[jacobkaufmann]

Looks like a straightforward change. I guess this will use the version from trin-core as opposed to the top-level trin? I don't think that's a problem, but one question that came up is whether we expect all of these packages to upgrade to new versions together?

[njgheorghita]

@jacobkaufmann Good question. Personally, I think so, all versions for all crates should be updated in lockstep.

1. Imo even though we have many crates, this is still one cohesive project. Theoretically these crates can be used individually, but I struggle to see this happening in any significant manner.
2. Code changes between releases seem likely to touch every crate. Even when that's not the case, I don't see any harm in updating the version of a subcrate

@carver any thoughts?

[carver]

@jacobkaufmann Good question. Personally, I think so, all versions for all crates should be updated in lockstep.

1. Imo even though we have many crates, this is still one cohesive project. Theoretically these crates can be used individually, but I struggle to see this happening in any significant manner.

2. Code changes between releases seem likely to touch every crate. Even when that's not the case, I don't see any harm in updating the version of a subcrate

@carver any thoughts?

👍🏻 to lock the version numbers to each other, at least for now.