Update invoke example values for numeric and byte types

[leighmcculloch]

What

Update example values for numeric and byte types that are presented to users in docs about a contract on the invoke command.

Why

The examples provided were a mix of rather random values, such as 'beefface123' for bytes, and some integers were exampled as '42', others contained negative signs which looked a bit confusing when seeing a suggestion to use a negative value for values in a contract that should never be negative.

Also, the BytesN command outputted invalid examples whenever the N was not event.

[Copilot]

Pull Request Overview

This PR updates example values for numeric and byte types used in the invoke command documentation for contracts. It replaces varied and sometimes confusing numbers (including negative values) with consistent, non-negative values and ensures byte examples are valid.

[Copilot]

Pull Request Overview

This PR updates example values for numeric and byte types in the documentation to provide more consistent and less confusing examples for users of the invoke command. Key changes include:

• Replacing mixed numeric examples (like 42 and -42) with a uniform value ("1") for the ScType numeric variants.
• Updating the byte examples to use a consistent 16-character hexadecimal string.
• Simplifying the logic for generating BytesN examples.