feat: Add entitlement management to Aviator application

[ankit2995]

Summary

This PR adds FCLI support for the Aviator Double Whiskey feature.

The change introduces a new fcli aviator app add-entitlement <application-id> command for incrementing an application's entitlement multiplier by one, and updates existing Aviator app output so multiplier-aware application state is visible in the CLI. The client continues to rely on the server for quota and multiplier business logic and only surfaces the returned application data.

Changes

• Added a new fcli aviator app add-entitlement <application-id> admin command
• Registered the new command under the existing aviator app command group
• Updated the Aviator gRPC client wrapper to call the new AddEntitlement RPC
• Updated the shared Aviator application proto contract to include multiplier-aware fields:
  • entitlement_multiplier
  • entitlements_consumed
  • effective_initial_quota
  • effective_monthly_quota
• Updated aviator app get output to show multiplier-aware fields
• Updated aviator app list output to show multiplier-aware fields
• Added help text and table output configuration for the new command
• Added a dedicated operation label for clearer error reporting during entitlement increment
• Used a numeric application id parameter type so invalid ids fail fast at the CLI boundary

User Impact

After this change, admins can increase application capacity directly from FCLI with:

fcli aviator app add-entitlement <application-id>

On success, the command returns the updated application record, including the new multiplier-aware fields. Existing aviator app get and aviator app list commands now also expose the multiplier-related state without requiring users to infer it externally.

Backward Compatibility

• Existing aviator app commands remain unchanged in shape
• aviator app get and aviator app list only gain additional output fields
• No multiplier or quota math is implemented in FCLI; the server remains the source of truth
• This keeps the change backward compatible while making Double Whiskey behavior visible in the client