core: frontend: MAVLink routers: allow managing tlog generation

### Current behaviour

The MAVLink Router and MAVLink Server [routing options](https://blueos.cloud/docs/latest/usage/advanced/#mavlink-endpoints) both automatically generate `.tlog` telemetry log files which uses space on the onboard computer for data that may be unnecessary, especially since telemetry logging is already often done by the control station software.

### Expected or desired behaviour

There is existing discussion in #2328 for handling log removal on a full disk, but it would also be useful to have some control over the generation aspect of the pipeline, allowing
- [ ] at least to disable tlog generation entirely, but
- [ ] ideally also providing an option to only generate them while the vehicle is armed (like the existing [`LOG_DISARMED`](https://github.com/ArduPilot/ParameterRepository/blob/main/Sub-4.5/Parameters.md#log_disarmed-enable-logging-while-disarmed) parameter for `.bin` log management in ArduPilot firmware), and
- potentially to start logging to a new file at
- [ ] arm/disarm state changes (like the [`LOG_FILE_DSRM_ROT`](https://github.com/ArduPilot/ParameterRepository/blob/main/Sub-4.5/Parameters.md#log_file_dsrmrot-stop-logging-to-current-file-on-disarm) ArduPilot parameter), and/or
- [ ] a max file size or logging duration (per [this comment](https://github.com/bluerobotics/BlueOS/issues/2328#issuecomment-2210359321))

### Additional Context
Issue suggested by @Williangalvani, together with the quote:
> I'd only enable them for troubleshooting

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.