feat(caller-reputation): support profile-first Caller Reputation API

[revanth-plivo]

Summary

• Adds four optional fluent-builder params to ProfileUpdater for the new profile-first Caller Reputation wire shape: enable_caller_reputation, vetting_provider, callback_url, callback_method
• Setter method names match the wire keys verbatim so the SDK is symmetric with the API surface across languages
• Bumps to 5.51.0; single new test profileUpdateWithCallerReputationShouldSucceed

Post-review wire shape

Profile.update(profileUuid)
    .enable_caller_reputation(true)
    .vetting_provider(java.util.Arrays.asList("at&t", "t-mobile"))
    .callback_url("https://example.com/cr/webhook")
    .callback_method("POST")
    .update();

• vetting_provider values are the customer-facing carrier keys "at&t" and "t-mobile" (case-insensitive on the API side; canonical lowercase in storage).
• Single profile-level callback URL replaces the earlier per-carrier callbacks: {carrier: {url, method}} map.
• Update Number is now attach-only for Caller Reputation — never calls RegisterBusiness in any case (approved, pending, failed, missing).

Test plan

• mvn test -Dtest=ProfileTest#profileUpdateWithCallerReputationShouldSucceed passes
• Existing profileUpdateShouldSucceed still passes (backward-compat)
• Manual end-to-end run against pre-prod: Profile.update(uuid).enable_caller_reputation(true).vetting_provider(Arrays.asList("at&t")).callback_url("https://…").callback_method("POST").update() returns 200 with caller_reputation_status in the response
• SELECT caller_reputation_callback_url, caller_reputation_callback_method FROM plivo_account_profile WHERE profile_uuid = ... shows the values landed in dbcfg

🤖 Generated with Claude Code