feat: add --force flag to push for all resources

[cjbell]

Description

Adds support for a --force boolean flag across all resource push commands. When provided, the flag bypasses environment restrictions and overwrites existing content in Knock by passing force: true to the API.

The flag is defined as a shared CustomFlags.force export in src/lib/helpers/flag.ts, following the same pattern as CustomFlags.branch, so the copy is centralized.

Commands updated:

• workflow push
• guide push
• partial push
• translation push
• layout push
• message-type push
• audience push
• push (top-level, which delegates to all of the above)

Implementation details:

• Shared force flag defined in src/lib/helpers/flag.ts with summary: "Force pushes the resource or resources to Knock, overwriting whatever is currently stored. If you're using this on a non-development environment, you should also ensure you `commit` the changes."
• Each push command references CustomFlags.force in its static flags
• All upsert* methods in api-v1.ts include force: flags.force in their query params (pruned when falsy)
• For audience push (which uses the @knocklabs/mgmt SDK directly), force is passed via request options query since the SDK's AudienceUpsertParams type doesn't yet include the force field
• The top-level push command forwards --force to all sub-commands via the args array
• Tests added for each resource push command verifying the force flag is passed through correctly

Tasks

N/A

Screenshots

N/A — CLI-only change, verified via automated tests.

  

[meryldakin]

Does this feel actionable enough as an instruction? Are we leaving it up to the users to do this or do we have some kind of guard around not messing this up?

[cjbell]

I think so? You can run knock push --force without commit then you'd just need to commit the changes in your non dev env, like you have to already in dev.