[Feature]: --signoff

Description

https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff

Suggested Solution

oco --signoff <email>

if this takes too long we can alias.

Alternatives

set in some config file

or have a way to not have oco prompt for push oco config set OCO_GITPUSH=false
.. then we can && git commit --amend --signoff && git push --force

Additional Context

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository#about-commit-signoffs

https://wiki.linuxfoundation.org/dco

For linux foundation, DCO is a requirement.

DCO sign-offs must be present on every single commit, or else the contribution will not be accepted.
A contributor agreement may be signed by a third party, like a company, on behalf of its employees, whereas the DCO is always an attestation by the author of the contribution.

Start at the CLI entry point for oco --signoff and inspect how commit creation, push prompting, and oco config set are currently handled. Clarify whether sign-off is an option, configuration setting, or both, then verify that the chosen behavior produces signed commits and preserves the existing push flow.