Add hazard for new NOT NULL columns requiring backfill

[catatsuy]

Description

Add a new hazard for schema diffs that add a new column as NOT NULL without a DEFAULT.
When this pattern is detected, the generated plan includes a clear warning and guidance for a safer online approach (add the column nullable, backfill data, then set NOT NULL using the existing online NOT NULL workflow).

Motivation

ADD COLUMN ... NOT NULL without a DEFAULT is commonly unsafe for non-empty tables and can lead to failed migrations or unexpected blocking.
pg-schema-diff already supports online NOT NULL changes for existing columns, but for new columns the tool cannot infer how to backfill data. This change helps operators notice the risk early and nudges them toward a staged migration.

Testing

• Added/updated tests to cover:

  • Adding a new NOT NULL column without a DEFAULT emits the new hazard and guidance.
  • Adding a new NOT NULL column with a constant DEFAULT does not emit the hazard (or follows the intended behavior).

• Ran the test suite locally (go test ./...).

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[bplunkett-stripe]

Tweaked and merged in here. You should be marked as a contributor on the repo!.Thank you for your contribution!

[catatsuy]

Thank you! @bplunkett-stripe