Feature #17269: Use subrun ranges instead of individual subruns in metadata
Add database support for subrun ranges
Add database support for subrun ranges. The simplest method would be to add a nullable max_subrun value, although this would complicate queries. Changing subruns to a Postgres range type would be more efficient, but more disruptive.
In most cases subruns aren't used in complex queries (or queried much at all), so extra complexity probably isn't an issue.