fix: improve network restrictions update logic

[maxmetcalfe]

What kind of change does this PR introduce?

API improvement

What is the current behavior?

Currently, running network-restrictions update will replace all existing restrictions with the provided list. This makes it easy to wipe all existing restrictions when adding a new one.

What is the new behavior?

network-restrictions update will now add the provided restrictions to the existing list. This matches the behavior of the "Add restriction" in the Supabase UI.

[coveralls]

Pull Request Test Coverage Report for Build 19432739386

Details

• 56 of 70 (80.0%) changed or added relevant lines in 2 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.07%) to 55.15%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
cmd/restrictions.go	0	2	0.0%
internal/restrictions/update/update.go	56	68	82.35%

Files with Coverage Reduction	New Missed Lines	%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 19427598841:	0.07%
Covered Lines:	6548
Relevant Lines:	11873

---

💛 - Coveralls

[sweatybridge]

This would be a breaking change for those who rely on the current behaviour. Could you introduce a new --append flag to the update command instead?

[maxmetcalfe]

thanks @sweatybridge. updated!