[WIP] Add console warnings for high MQTT publish rates

[Claude]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>high mqtt publish rates should log console warnings</issue_title>
<issue_description>The overall goals is to discourage users from overloading the Mqtt network with unnecessary messages. We'd like to cap those messages ideally before publishing. Any message we deny publishing for performance purposes we should warn the user of the reason. We also want to do be wary of the overhead cost of evaluating each message which may cost local performance. Can we:

• globally deny messages over 100ms average over 1 second per object id, or is it better to only warn if the threshold is crossed?
• globally deny messages with the same json payload, sans timestamp, since they are not providing any updates to the scene graph?</issue_description>

Comments on the Issue (you are @claude[agent] in this section)

• Fixes high mqtt publish rates should log console warnings #129

[mwfarb]

@claude[agent] did you have any proposal?

[mwfarb]

@claude[agent] This PR is empty. Please begin again.