Refactor rule cases to use a slice

[jranson]

Currently rule cases are modeled as a map with keys that are only used to name the rule case (and have no effect on the rule execution). This should be switched to a slice for simplification and to avoid inconsistencies in the case ordering during execution.

[Elia-Renzoni]

I'm new to the codebase and find the project fascinating. I'd be happy to take care of this issue if that's alright.

[jranson]

@Elia-Renzoni thanks for volunteering for this - we'd love the help. It would be a good idea to wait until we merge #851 before you get started on it, since that will include a separate bugfix for rules that is a pre-requisite to this change.

[Elia-Renzoni]

Ok, thanks! Will wait for #851.

[jranson]

@Elia-Renzoni we ended up fixing the rules panic issue in its own PR (#864), so the main branch is now ready to work on this issue.

In addition to updating the functional code, be sure to update example usage and documentation. Specifically:

• deploy/kube/configmap.yaml
• docs/developer/environment/trickster-config/trickster.yaml
• docs/rule.md
• examples/conf/example.full.yaml
• testdata/test.routing.rules.conf

[Elia-Renzoni]

Got it, I’ll pick it up from the updated main and make sure to update the code and all the listed files.

[jranson]

fixed in #865