Spike: Rust Cleanup

[cpyle0819]

Identify the set of changes necessary for #3465

[DavidSouther]

• Folder, crate, and service names should all be the same.
  • sitewise != iotsitewise
• Tracing for all binaries
  • All binaries should at minimum have tracing_subscriber::fmt::init();
  • Describe common RUST_LOG idioms, like aws_smithy_http_tower::dispatch=trace
  • Provide guidance on a tracing_subscriber configuration that works with AWS CloudWatch Agent
• StructOpt is deprecated in favor of clap_macro.
• Error handling is a lot of upwrap()s and expect()s.
  • ? and Results with the new Error handling RFC
• All examples are "CLI Apps", which adds a lot of unnecessary cognitive overhead to understanding the examples.
  • Minimize args to the bare minimum for the example
  • Batch two or three examples into mini-scenarios
    • Confirm with wider team
• No unit testing.
  • Most MVPs have little to no logic, and would be better suited to integration testing.
  • Scenarios should have a high level structure, and allow mocking the clients.
• No integration testing.
  • Integration tests should call scenarios' high level structure functions, and assert that appropriate changes have happened in AWS resources.
  • Integration tests should be #[ignored] by default, as they will incur AWS usage charges.

[DavidSouther]

Closing for the sprint and building tickets from identified bullets