Identify another messy refactor on the horizon

Packages can either output new APIs or expect them in the cluster.

Examples of packages which
- output APIs: Gateway API, which installs various versions of
  gateway.networking.k8s.io resources.
- take APIs as input: app-template, which queries the cluster to
  choose v1a2, v1b1, or v1 for its HTTPRoute (etc.) objects.

("Packages" here collectively refers to Helm charts and YAML bundles.)

I will have to impose strict ordering on them, i.e., build the former
before the latter.

flake.nix

@@ -29,8 +29,11 @@
     rake = import ./lib/rake.nix;
   in
     {
+      # systemData = rake.leaves ./system;
+      # serviceData = rake.leaves ./services;
       releaseData = rake.leaves ./releases;
       repos = rake.leaves ./charts;
+
       namespaces = rake.namespaces {
         root = ./releases;
         extraMetadata = import ./namespaces.nix;