docs: Point Docker README licensing sections at the trial form

[andrie]

Summary

The Connect, Workbench, and Package Manager Docker READMEs (rendered as the description on Docker Hub) tell first-time users that they need a "valid License" but never say where to get one. With the built-in 45-day trial removed under Project Gateway, this PR adds a one-sentence pointer to https://posit.co/trial-license/ in each README's Product Licensing intro.

It also reworks a stale comment in package-manager/Dockerfile.ubuntu2204 that referenced the built-in trial; the new wording preserves the operational meaning (userspace init can fail; activation can be retried) without referencing trials.

Changes

File	Change
connect/README.md	Add trial-license pointer sentence to Product Licensing intro
workbench/README.md	Same
package-manager/README.md	Same
package-manager/Dockerfile.ubuntu2204	Rework line-49 comment to drop trial reference

What's left as-is

The example license-manager status output (with Has-Trial / Trial-Type lines) is unchanged. The binary still prints those fields during the 7-day transitional period, so the example is still accurate. Best to revisit when the binary output itself changes.

Cross-references

• Tracking: TWPM-434 — Documentation updates for Project Gateway
• Wave 2 PRs already in flight: posit-dev/connect#39378 (approved), rstudio/package-manager#17931, rstudio/rstudio-pro#11013

Closes #1036

[andrie]

cc @bschwedler @glin @sarahsdao — requesting review.

[andrie]

Diagnosed the CI failures: every red "Build, Test, and Push" job is hitting Snyk authentication timeout (SNYK-CLI-0000: authentication failed (timeout)). The Snyk CLI tries to open an interactive browser auth flow because the SNYK_TOKEN secret isn't reaching the job, then times out after 2 minutes. Example: run 25565446955 / Connect job.

Notes:

• This is unrelated to the changes in this PR — it only edits 3 README files and one Dockerfile comment.
• The Lint workflow on the same SHA passed, so the issue is specific to the Snyk-using build workflows.
• Main branch CI is also intermittent: today's 07:04 UTC run succeeded but 05:18 UTC failed, suggesting the Snyk auth path is flaky generally (or the secret isn't being passed to PR-triggered runs).
• I tried gh run rerun --failed on both failed workflow runs; both returned "workflow file may be broken," so I can't retrigger from here.

@bschwedler @ianpittwood — could one of you check whether SNYK_TOKEN is configured to be available on pull_request-triggered runs, or push an empty commit to retrigger? Happy to push a no-op myself if that's the preferred path.

[ianpittwood]

@andrie we may have finally had our plan end for Snyk Container. I'll take a look tomorrow to fix it.

[ianpittwood]

@andrie if you can rebase your change, it should work now. I didn't notice before that this was a fork though so there may still be permission issues.