feat(robot-server): separate can logs from other serial logs

[caila-marashaj]

Overview

Currently, CAN messages are stored in the same logging file as serial communications from modules. This means that if, for example, an abr bug occurs, and the logs are grabbed even a few minutes later, a present thermocycler will have sent so many status messages that the CAN messages from when the error happened are pushed out of the logs.

Let's give the CAN messages their own file so we have a better idea of what happened when we need to look at logs.

Changelog

• add an entry for the existing opentrons-api-serial-canbus logger to the logs router
• the change in the serial log's maxbytes from 1000000 to 5000000 was actually done in an attempt to capture CAN messages along with the serial messages, so revert that

[sfoster1]

Looks good if it works on a machine! Thank you!