feat: Asset agnostic rule configs

[niliayu]

This PR adds the ability to define rules in YAML separate from the main telemetry config, so that rules may be referenced and reused in the context of multiple assets.

A rule that's defined in a namespace can be referenced in the main telemetry config like so:

  - namespace: voltage
     name: undervoltage
     channel_references:
       - $1: *vehicle_state_channel
       - $2: *voltage_channel

With the corresponding rule defined in a separate YAML like so:

namespace: voltage
   - name: undervoltage
     description: Checks for undervoltage while accelerating
     expression: $1 == "Accelerating" && $2 < 40
     type: review

Or if the user wants to instantiate rules in python directly, the load_rule_namespaces function has been added that will allow them to provide a path to the directory containing their rule YAMLs and load them into memory:

   rule_namespaces = load_rule_namespaces(
         [
             RULE_NAMESPACES_DIR,
         ]
     )

    RuleConfig(
                 name="overvoltage",
                 namespace="voltage",
                 namespace_rules=rule_namespaces,
                 channel_references=[
                     # INFO: Can use either "channel_identifier" or "channel_config"
                     {
                         "channel_reference": "$1",
                         "channel_identifier": vehicle_state_channel.fqn(),
                     },
                     {
                         "channel_reference": "$2",
                         "channel_config": voltage_channel,
                     },
                 ],
             ),

You can see examples of this rules in dev in this run: https://dev.app.siftstack.com/share/3xBUAIQ

[niliayu]

Just rebased the branch since it was getting a bit stale.

[niliayu]

@marcsiftstack :
So one of the next things I was looking to do here was update the python ingestion example to be able to read in the same rule yaml CSVs. I made a load_rule_namespaces function that's somewhat similar to the load_named_expression_modules one used here, but I realized I put the logic to reassemble the rules from their namespaces in the yaml-specific TelemetryConfig._from_yaml. I basically set this up so that for the yaml example, the TelemetryConfig & RuleConfigs get reassembled from yaml to look exactly the same as if the rules had been defined in one flat yaml to begin with. So maybe for now that means we need to do some similar logic when creating the RuleConfigs for the example namespace rules, but I haven't had quite enough time to think about how best to make this look for now. I could definitely be missing something super simple here to make this work though!

Edit: This has now been addressed!