[Feature] Collapse the duplicated workflow bash into composite actions

Several large bash blocks are copy-pasted across the workflow files, which means a fix to one has to be remembered in five other places.

The "check for license errors" block, roughly 20 to 25 lines that finds the container, greps its log for expired or invalid license text and writes a step summary, appears in workbench-smoke.yml, connect-smoke.yml, packagemanager-smoke.yml, connect-integration.yml, example-report.yml and preview.yml. Only the product name, container filter and secret name differ, so this is close to pure string substitution.

The workflow-summary block that parses the JUnit XML and builds the emoji results table, roughly 35 to 45 lines, appears in connect-smoke.yml, packagemanager-smoke.yml, workbench-smoke.yml, connect-integration.yml and example-report.yml. This is the single largest duplicated block.

Three smaller ones: the set-matrix job is effectively identical between connect-smoke.yml and workbench-smoke.yml and the same shape in packagemanager-smoke.yml and mock-idp-e2e.yml; the "update job title with resolved version" github-script step is repeated in three smoke workflows with only the matrix field name differing; and the four-part status aggregator job is repeated in four workflows, though that one embeds product-specific wording and is more entangled.

A handful of composite actions under .github/actions/ would collapse most of this. There is now a local composite action in the tree to follow as a pattern. Worth doing incrementally, highest-duplication block first, rather than as one large change.

Start by reading the existing local composite action under .github/actions/ and compare the license-check block across workbench-smoke.yml, connect-smoke.yml, packagemanager-smoke.yml, connect-integration.yml, example-report.yml and preview.yml. Extract the highest-duplication block first, then verify the affected workflows retain their product-specific inputs, license checks and step summaries. Continue incrementally with the workflow-summary block once the first action is working.