Add new numeric constants for octal and binary to chialisp

[prozacchiwawa]

This will add new octal and binary constants to chialisp compilation. Since the data representation of clvm values uses virtually every string as some kind of valid value, a new *bitconst* include is provided to enable interpretation as octal and binary.

The rule for these bit constants is that if a completely unnecessary zero is used as left padding that appears in a new byte, then the constant has that left zero byte.

In modern, it's enabled by the sigil *standard-cl-nc25* , in classic by *bitconst* (this is the first sigil affecting classic).

Since the first 0 is required, 0o0 and 0b0 are () not 0x00.
0b00 and 0o00 are 0x00.

Consider the octal constant 0o377, which is 0b11111111, this is -1 or 0xff.
If you add a zero to 0o377, 0o0377, then this is 0x00ff. 0b011111111 is also 0x00ff.

---

Note

Medium Risk
Touches core parsing/printing paths for both classic IR and the modern compiler, so subtle parsing or round-tripping regressions are possible even though the feature is gated behind dialect/include flags.

Overview
Adds opt-in binary (0b...) and octal (0o...) numeric literals that compile to byte-atoms with defined left-padding semantics.

This introduces a NEW_BIT_CONSTANTS language flag and threads it through classic tooling (read_ir/IRReader, assemble/disassemble, and stage-2 operators) and the modern compiler parser (parse_sexp_flags) so dialect detection can re-parse with the correct numeric rules. New dialect sigils *standard-cl-nc25* (modern) and *bitconst* (classic) enable the behavior, and a dedicated test suite (tests/classic/bitconst.rs) validates parsing, disassembly round-trips, and fuzzes padding edge-cases.

^{Written by Cursor Bugbot for commit e04b8c9. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[Quexington]

I won't pretend to understand the semantics of this change but I approve it conceptually.