Generic udev Configuration

[kate-goldenring]

What this PR does / why we need it:
We currently only have documentation and a sample Configuration for how to use the udev discovery handler to discover usb cameras. This adds a generic sample udev Configuration and documentation on how to use it to find any device discoverable by udev. It also modifies the name of the ONVIF configuration from onvif-video to onvif. This pr creates a standard of providing a generic configuration for each protocol that can be applied to a cluster with helm via --set <protocol>-enabled=true. Additionally, it sets the standard that a broker image must be specified on installation, else Akri will advertise the resources but not deploy brokers. Finally, it creates a standard of creating a <protocol>-configuration.md document for each generic configuration provided.

Special notes for your reviewer:
We've received questions on how to use udev to discover audio devices (ref #33). Modifying the udevVideo configuration seems illogical and starting from an empty yaml is a big barrier to entry.
closes #68
ref #69

If applicable:

• this PR contains documentation
• this PR contains unit tests
• added code adheres to standard Rust formatting (cargo fmt)
• code builds properly (cargo build)
• code is free of common mistakes (cargo clippy)
• all Akri tests succeed (cargo test)
• inline documentation builds (cargo doc)
• version has been updated appropriately (./version.sh)

[kate-goldenring]

I think it would make sense at this point to remove the udevVideo configuration. Instead in the udev video sample documentation, we can walk through the steps of setting the environment variables (udev values would need to modified to be able to configure this), broker image, and Configuration name. Thoughts?

[kate-goldenring]

I think it would make sense at this point to remove the udevVideo configuration. Instead in the udev video sample documentation, we can walk through the steps of setting the environment variables (udev values would need to modified to be able to configure this), broker image, and Configuration name. Thoughts?

I wonder if we should phase out the udevVideo configuration, since it is part of our e2e demo. Some people may be currently running it. I could change the e2e to use just udev and then maybe we remove udevVideo entirely for our next release. That bodes the question: do be make onvifVideo onvif?