feat(javascript): align buffer read/write API with Java naming

[miantalha45]

Summary

Aligns the JavaScript buffer API with Java and other xlang implementations by using explicit read* / write* method names only. No compatibility aliases; one-shot breaking change.

Changes

• BinaryWriter (lib/writer/index.ts): Removed short-name aliases (int8, uint8, int16, etc.). Public write API is now only the existing write* methods (e.g. writeInt8, writeUint8, writeInt32, writeFloat64, writeGetCursor, etc.).
• BinaryReader (lib/reader/index.ts): Removed short-name aliases. Public read API is now only the existing read* methods (e.g. readInt8, readUint8, readInt32, readGetCursor, readSetCursor, readSkip, etc.).
• Codegen (lib/gen/builder.ts): BinaryWriterBuilder now emits write* calls (e.g. bw.writeInt8(...)); BinaryReaderBuilder now emits read* calls (e.g. br.readInt8(), br.readGetCursor()).
• Tests (test/io.test.ts): Updated dynamic writer calls from writer['uint${x}'] / writer['int${x}'] to writer['writeUint${x}'] / writer['writeInt${x}'].

Requirements met

• Writer methods use write* prefix (e.g. writeInt8, writeUint32).
• Reader methods use read* prefix (e.g. readInt8, readUint32).
• One-shot breaking rename; no old names, aliases, or deprecation shims.
• All internal call sites, codegen, and tests updated.
• Runtime behavior and performance unchanged.

Testing

• cd javascript && node ./node_modules/.bin/jest --ci — all 18 suites pass (112 tests, 1 skipped).

Fixes #3345

[chaokunyang]

Could you also rename such methods?

[miantalha45]

Sure

[miantalha45]

I have done this.

[chaokunyang]

LGTM