fix(diff): include view reloptions changes

[pjpjq]

Summary

• Compare source and target view pg_class.reloptions for non-pg-delta db diff.
• Generate ALTER VIEW ... SET/RESET (...) for reloption-only changes on existing views.
• Add regression coverage for regular views, materialized views, schema filtering, and the connected diff path.

Fixes #5476.

Tests

• cd apps/cli-go && go test ./internal/db/diff ./internal/db/pull ./cmd

[SahilArate]

Nice approach the post-processor pattern is the right call here given migra's blind spot on pg_class.reloptions.
A few thoughts that might help before merge:

1. No-op guard: if both source and target have reloptions = NULL, the diff should be a clean no-op. Worth adding a test case to confirm there's no spurious SET () emitted.
2. Dropped view edge case: if a view exists in target but not source (i.e. it's being dropped), the post-processor shouldn't emit an ALTER VIEW SET for it — the drop statement from migra already handles it. A guard on view existence in both catalogs would be defensive here.
3. Multiple reloptions at once: if security_invoker and another reloption both change in the same diff, the generated SQL should batch them: ALTER VIEW foo SET (security_invoker=false, check_option=cascaded) rather than two separate statements.
4. RESET vs SET: when a reloption is removed entirely (not just changed), RESET is the correct SQL. Worth verifying the test covers the full remove case, not just value swap.
   Happy to help test or iterate on any of these!