feat(license): set default key in production to enable paid features in clusters with a maximum of 4 CPU cores

[BugenZhao]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Based on #20276, a license key with Paid tier and CPU limit of 4 is set by default for production cluster in this PR. This allow users' evaluation of paid features on a small scale.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

RisingWave now includes a trial of paid features for clusters with up to 4 compute node CPUs for users to evaluate those features on a small scale. When there are more CPUs in the cluster, the trial will be unavailable for both existing and future jobs, and users will need to acquire a license key to continue using the paid features.

For a fresh deployment, this comes automatically. For an existing deployment upgrading to this version, users may need to refresh the license key by executing ALTER SYSTEM SET license_key TO DEFAULT; in the SQL shell to activate the trial.

[BugenZhao]

• feat(license): set default key in production to enable paid features in clusters with a maximum of 4 CPU cores #20296 👈 (View in Graphite)
• feat(license): invalidate license when cpu exceeds limit instead of rejecting new compute nodes from joining #20276
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Hi, there.

📝 Telemetry Reminder:
If you're implementing this feature, please consider adding telemetry metrics to track its usage. This helps us understand how the feature is being used and improve it further.
You can find the function report_event of telemetry reporting in the following files. Feel free to ask questions if you need any guidance!

• src/frontend/src/telemetry.rs
• src/meta/src/telemetry.rs
• src/stream/src/telemetry.rs
• src/storage/compactor/src/telemetry.rs
  Or calling report_event_common (src/common/telemetry_event/src/lib.rs) as if finding it hard to implement.
  ✨ Thank you for your contribution to RisingWave! ✨

---

This is an automated comment created by the peaceiris/actions-label-commenter. Responding to the bot or mentioning it won't have any effect.

[gru-agent]

This pull request has been modified. If you want me to regenerate unit test for any of the files related, please find the file in "Files Changed" tab and add a comment @gru-agent. (The github "Comment on this file" feature is in the upper right corner of each file in "Files Changed" tab.)