Add dependency to 0006 to avoid order issue

[CarolineDenis]

Fixes #6898

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

[melton-jason]

This generally works, assuming we accept the risk users who have already ran the patches/0006 migration would need to resolve the migration manually.
The impact might be very high: this might affect Specify 6, Specify 7, as well as any tools that use the Specify 7 API (#6888 (review)).
The subset of users this would affect would hopefully be small: internal and any who have pulled from main (or a branch derived of main) since #6384 was merged (June 24, 2025).

Ideally, I think this should be a separate migration altogether (which has dependencies on both patches/0006 and specify/0035) so that even if someone did pull from main since #6384, they would encounter no problems and don't have to manually resolve the version issue in the database.

Given that the risk that a user has pulled main may be sufficiently small (not included in a release, and within main slightly over 2 weeks), this approach is practically probably fine 🤞