New contracts now fire the "Contract stage changed" webhook

What Changed

The “Contract stage changed” (contractsStageUpdated) webhook previously
fired only when an existing contract moved between stages. A brand-new
contract entering its very first stage delivered the contractPipelineStatusesCreated
event but not “Contract stage changed”, so integrations (Zapier, Make, or custom
endpoints) subscribed only to “Contract stage changed” never heard about newly
created contracts.

Now a contract’s first stage assignment counts as a stage change:

• Creating a contract with a stage fires the “Contract stage changed”
  (contractsStageUpdated) webhook, keyed to the contract, in addition to the
  existing contractPipelineStatusesCreated event.
• Later stage moves are unchanged — no duplicate deliveries.