fix: add fixed order when selecting types to drop (fixes issue #2207)

[hammerlscs]

What kind of change does this PR introduce?

Adds a fixed order when selecting the types to drop for the supabase db resetcommand.

What is the current behavior?

Currently, the order is not defined and this can lead to errors when dropping types. (More details: #2207)

What is the new behavior?

The types are dropped in a fixed order. The order is the number of type dependencies ascending.

The idea is that "base" types are always dropped before e.g. "array" types which have at least 1 type dependency to its "base" type.

[coveralls]

Pull Request Test Coverage Report for Build 8828587699

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 58.196%

---

Totals
Change from base Build 8810766962:	0.0%
Covered Lines:	6511
Relevant Lines:	11188

---

💛 - Coveralls