Epic: extract bricks to their own repositories #305

Current State

Bricks are the unit of optional engine functionality. Those with an independent release cadence should live in their own repositories, the way Gaya is being extracted (#80, #78) and the KTX2 and OAP libraries already were.

Tasks

• Brick extraction: OBJ importer #303 OBJ importer
• KTX2 and OAP: consume the published packages (Assets: KTX2 container replaces .amtex (managed reader and writer) #31)
• Brick extraction: Localization #302 Localization
• Assets: ASTC texture bake with astcenc #278 ASTC texture bake (editor brick)
• Android: org.mass4.turian.android brick and AndroidBuildPlatform #254 Android brick, after .NET 11 GA
• Brick extraction: in-game UI brick #304 In-game UI brick
• For each: publish a package, consume it from Turian, enforce the boundary in CI (Gaya: enforce the Gaya → Turian dependency boundary in CI #77)

Acceptance Criteria

• Each extracted brick builds, tests and releases independently, and CI fails if the engine references its code directly.

Related

#80, #78, #77, #47