require resources.topology and rates.topology to be filled

[majewsky]

This was not upheld in some test scenarios, which might cause confusion down the line.

[github-actions]

Merging this branch will not change overall coverage

Impacted Packages	Coverage Δ	🤖
github.com/sapcc/limes/internal/collector	83.52% (ø)
github.com/sapcc/limes/internal/db	81.29% (ø)

---

Coverage by file

Changed files (no unit tests)

Changed File	Coverage Δ	Total	Covered	Missed	🤖
github.com/sapcc/limes/internal/db/migrations.go	0.00% (ø)	0	0	0

Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code.

Changed unit test files

• github.com/sapcc/limes/internal/collector/capacity_scrape_test.go
• github.com/sapcc/limes/internal/collector/scrape_test.go

[wagnerd3]

Lucky you, I just recently introduced the fallback to FlatTopology on app layer with the changing-units PR 😄 https://github.com/sapcc/limes/blob/master/internal/core/cluster.go#L703

I think this should be safe to rollout without migrating any data, as the limit-only rates are always written on startup and should have been migrated.