Camera lights, leaving meetings, and console warnings

This line logs a console.warn message when an action occurs in a state that does not support a transition for the given action. It will log this warning if an Update happens in the Disconnecting state:

No transition found from Disconnecting with Update

I suspect this warning is occurring frequently in our case because of the way we leave meetings:

await  audioVideo.stopVideoInput();
await  audioVideo.stopAudioInput();
audioVideo.stop();

This feels paranoid, but I am doing it because the [documented way](https://aws.github.io/amazon-chime-sdk-js/modules/apioverview.html#:~:text=To%20stop%20the%20meeting%20session%2C%20call%20meetingSession.audioVideo.stop().) to end meetings is apparently incomplete, given [further documentation](https://aws.github.io/amazon-chime-sdk-js/modules/faqs.html#after-leaving-a-meeting-the-camera-led-is-still-on-indicating-that-the-camera-has-not-been-released-what-could-be-wrong:~:text=meetingSession.audioVideo.stopVideoInput()%3B) that seems justified given my experience and also several stackoverflow questions on the topic [1], [2] (bottom answer is where I take my code from).

I have two questions:

Is the WARN level here correct? I can imagine situations where actions may happen concurrent with states for which there is no defined transition, and that being a benign situation.
What is the one true way to fully leave a meeting client-side in the way users would expect, without that logic creating console.warn messages in our logs?

Note: From my perspective as a user of this API , I do think fully leaving meetings (and releasing all employed resources) should be a single line of code. Perhaps I am missing something? But if not, the percentage of users who are googling in frustration after chapter 4 left their camera light running has got to be close to 100%.

aws / amazon-chime-sdk-js

Camera lights, leaving meetings, and console warnings #2794