Changed: Refactor workflow structure and extract artifact naming logic

[Sewer56]

• Extract artifact name generation to scripts/get-artifact-name.sh with named parameters
• Refactor action.yml to use new artifact naming script instead of inline logic
• Consolidate test-friendly-names.yml and test-unfriendly-names.yml into test-artifact-names.yml
• Add comprehensive artifact name testing with 18 matrix combinations (9 targets × 2 friendly-name settings)
• Rename test-build-workflow.yml to test-build-options.yml and remove redundant test jobs

To fix the problem, add a permissions: key to the workflow root, specifying the minimal permissions required. For workflows that only check out code and do not interact with issues, pull requests, or perform deploys or artifact uploads, contents: read is sufficient. This block should be placed after the name: or on: sections, and before jobs:. In this workflow's structure, adding it after the on: block is standard. No method, import, or definition is required, just YAML structure changes in .github/workflows/test-artifact-names.yml.

The best way to fix this problem is to add an explicit permissions block to the workflow file .github/workflows/test-artifact-names.yml, either at the root level (to affect all jobs) or to the jobs that do not have their own specified permissions. Since none of the jobs appear to need write access—for example, they simply run shell scripts to verify artifact names—it is sufficient to set contents: read (the minimal required permission for most workflows that only need to read code). Place the block immediately before the jobs: key for best readability and maintainability. No other code or imports need to be changed; this is entirely a YAML config edit.