feat(resource): support custom generated record names

[johanpel]

Description

Allow ResourceBuilder to use explicit usage and bounds record names through with_record_names. new retains the default {Resource}Usage and {Resource}Bounds naming scheme.

Also expose Resource::constraint_data for consistent constraint serialization.

Written by Codex.

Related issues

This is useful because in #427 it can be leveraged to provide custom names for these record types.

[coderabbitai]

📝 Walkthrough

Walkthrough

Changes

Resource construction and constraint encoding

Layer / File(s)	Summary
Configurable record names and build validation crates/resource/src/builder.rs	ResourceBuilder supports default or explicit usage and bounds record names, validates duplicates for bounded resources, updates BuildError, and adjusts tests.
Constraint payload encoding crates/resource/src/lib.rs	Resource::constraint_data() serializes resources to JSON and returns serialization errors.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

• rapidsai/quent#387: Changes the related ResourceBuilder record-name handling and BuildError behavior.

Suggested reviewers: mbrobbel, dhruv9vats

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding custom record-name support for resources.
Description check	✅ Passed	The description covers the change and related issue, but omits the template's Testing and Screenshots sections.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[johanpel]

/merge