Make it possible to initialize COUNTER with a custom value

[igor-casper]

With the changes introduced in #1 , the request ids are ordinal, counted from 0. This is problematic for the CLI, which is stateless and short-lived, as it will always attempt to send a request with id=0. This PR adds the ability to initialize the internal counter with a specified value, so that the CLI can replicate its prior behavior of randomly picking out an id. It's also useful for consumers of the binary port access library facing similar issues.

See:

fn main() {
    let args = args::Args::parse();
    casper_binary_port_access::initialize_request_id(rand::rng().random());
    let result = match args.commands {
    // go on as usual
    // ...
}

[gRoussac]

@igor-casper Cool thanks, I was about to do he same as per your suggestion! LGTM, still this request id is now nested in the response request after coming changes and I think it should be in the response header like the tag and protocol version but I let you guys decide.