RSDK-6170 - add debug log support

[stuqdog]

Adds support for server-side debug logging.

Note to reviewers: this PR gets us 90+% of the way to where we want to be. The problem is that a few methods (get_properties and is_moving, e.g.) do not take extra as a param. I spent some time brainstorming but I don't see a way to support adding debug logs for these without adding new params to the methods (which would be breaking). Even if we decided to break things, we'd either have to add extra to these (which would be misleading to users) or add a special field to these (which would have unclear/ambiguous utility to many implementers and would create inconsistency in our implementation that could be confusing for users). As such, I've opted to go with the "good enough" approach; we can cross this bridge if/when if a user desperately needs debug log support for these particular methods sometime in the future.

example code:

#include <viam/sdk/common/proto_type.hpp>
#include <viam/sdk/components/motor.hpp>

auto robot = connect();

auto m = robot->resource_by_name<Motor>("<my-motor-name>");
// "my-cool-key" is optional; if not provided, a random key will be created
AttributeMap with_key = debug_map("my-cool-key"); 
// alternatively if you already have a map you could call `add_debug_entry(my_map, "my-cool-key");` 
m->go_for(100, 2, with_key);

example output:

Flybys:

• remove some include/using invocations
• Add extra-less, inline Arm::move_to_joint_positions

[stuqdog]

@dgottlieb fyi!

[stuqdog]

Just noticed that the commit hash starts with 993355757. which isn't important at all but I kinda like it.

[lia-viam]

Mostly minor changes, maybe we should also add a change to one of the unit tests using a peek_debug_key parameter or similar?

[lia-viam]

slight typo with the close paren

[lia-viam]

This and the one above should probably pass the parameter in the same way?

[lia-viam]

Suggested change

	return debug_map(debug_key);
	return debug_map(random_debug_key());