Fix Official Library staging readiness

[suguanYang]

Summary

• publish only ready Official Library sources that have backing demo payloads, so planned parse failures like Information Theory do not appear in the public catalog
• allow valid Dashboard JWT users to use the API immediately by provisioning the API-owned reference user row with an idempotent insert
• cover the catalog ready-only contract and Dashboard JWT first-use path in contract tests

Verification

• uv run pytest apps/api/tests/contract/test_demo_documents_contract.py apps/api/tests/contract/test_job_creation_contract.py -q
• uv run ruff check apps/api/app/services/auth/current_user_authentication_service.py apps/api/app/services/demo/official_library_catalog.py apps/api/tests/contract/test_demo_documents_contract.py apps/api/tests/contract/test_job_creation_contract.py
• uv run pyright apps/api/app/services/auth/current_user_authentication_service.py apps/api/app/services/demo/official_library_catalog.py apps/api/tests/contract/test_demo_documents_contract.py apps/api/tests/contract/test_job_creation_contract.py
• make lint
• make typecheck
• git diff --check

[suguanYang]

Closing per review: this Dashboard JWT user-reference provisioning is not the correct fix for the Official Library task and should be handled as a separate staging auth/data mismatch issue.