Build Tizen native dependencies in a Docker container instead of on the build agent

[mattleibow]

Context

Today the Tizen native libraries are built directly on the build agent using a locally-installed Tizen Studio (C:\Users\VssAdministrator\tizen-studio\tools\llvm-10, x86_64-linux-gnu-gcc-9.2). This couples the build to agent-provisioned tooling and pins us to an old, C++20-incapable toolchain (clang 10 / gcc 9.2 libstdc++).

Goal

Move the Tizen native build into a Docker container, the way the WASM build already works:

• scripts/infra/native/wasm/docker/Dockerfile
• scripts/infra/native/wasm/install-emsdk.sh
• Docker usage in scripts/azure-templates-jobs-bootstrapper.yml / scripts/azure-templates-jobs-wasm-matrix.yml

Benefits:

• Reproducible, version-pinned Tizen toolchain that's independent of the agent image
• Gets the toolchain "off the agent machine"
• Enables bumping the Tizen toolchain to a C++20-capable one (unblocks restoring the PDF backend — see companion issue)

Scope

Investigate feasibility and implement a containerized Tizen native build. Independent of the m150 update; targets main.