Browser log warnings

[blackfalcon]

General Support Request

There is a growing list of log warnings in this repo that should be reviewed.

      Multiple versions of Lit loaded. Loading multiple versions is not recommended. See https://lit.dev/msg/multiple-versions for more information.
      Element auro-dropdown-2_10_5 scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.
      Element auro-input-2_17_6 scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.
      Element auro-calendar scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.
      Element auro-calendar-month scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.
      Element auro-calendar-cell scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.
      Element auro-datepicker scheduled an update (generally because a property was set) after an update completed, causing a new update to be scheduled. This is inefficient and should be avoided unless the next update can only be scheduled as a side effect of the previous update. See https://lit.dev/msg/change-in-update for more information.

Possible Solution

Review these logs and determine the severity.

Additional context

n/a

Exit criteria

This issue can be closed once the warnings have been reviewed and recommendations are documented.

[Patrick-Daly-AA]

This is an issue we need to look at more wholistically across multiple components. This is not just a datepicker issue. This error isn't due to new code, it's from a new version of Lit warning us of inefficient code.