AZVIDT06 - BK10 Monitor font offset fix

Hardware observation: V05 displayed AZBK as QjR[, a consistent +16 character
mapping offset. Original strings are already 7-bit ASCII.

BK-0010 Monitor-10 font has 8x10 glyphs (10 bytes per glyph).
ASCII space (040 octal, 32 decimal) starts at octal address 112276.
PrintChar computes font_addr = FONTBASE + ASCII_code*10 decimal.
Thus FONTBASE = 112276 - (32*10) = 111576 (octal).
V05's 112036 was 0240 octal (160 decimal, 16 glyphs) too high.

Scope:
- Video mode 012100 unchanged.
- ROM pages 134/135 mapped into 100000/110000 unchanged.
- 160000/170000 untouched.
- Rendering and keyboard logic unchanged.
- All UI strings remain 7-bit English ASCII (already were ASCII in V05).
- All 60 video-mode control words unchanged; tests are still stubs.
- Updated displayed version to AZVIDT06.

Hardware validation:
1. Assemble AZVIDT06.asm using Turbo8 (not available here).
2. Launch on real AZBK and look for readable title AZBK VIDEO CONTROLLER TEST.
3. Verify SELECT VIDEO MODE, EXIT TO ANDOS and help text.
4. ENTER opens 15x4 mode grid. Arrow keys should navigate.
5. SPACE or KT should exit to ANDOS via JMP @#100000.
6. Please send screen photo if text is still incorrect.

Static validation PASS:
- Strings use printable ASCII only.
- 60 video-mode code words retained.
- Space glyph font pointer calculated at 112276 (octal).
- V05 font base differs from V06 by exactly 16 glyphs.
- This release changes no low-level write path.
Hardware execution and Turbo8 assembly remain unverified.
