Stripe CLI trigger command cannot fire events with real customer or subscription IDs attached

stripe-cli trigger fires synthetic fixture events -- every invocation creates throwaway API objects with random IDs, metadata, and amounts that have nothing to do with your live or test account state. Developers then write webhook handlers that chase real database records by customer or subscription ID, but the triggered event carries an ID that does not exist in their DB. The result: you cannot exercise your actual handler logic locally without either setting up a public tunnel and waiting for a real transaction, or hand-crafting raw JSON payloads and bypassing signature verification entirely. This CLI resolves that by letting you select an existing object from your Stripe test account -- a customer, a subscription, a payment intent, a price -- and compose a valid, signature-verified webhook event payload around it, then deliver it to your local endpoint. The event body is structurally identical to what Stripe would send, populated with real fields from the live object, so handler logic that looks up records by customer ID, updates subscription state, or routes on price metadata works correctly under test for the first time without a tunnel.