42dot AU Changes During Testing

[chasingZZZs]

Description

During testing, some changes were made to the pytest tests and the implementation of device_uio.py to allow the tests to execute. It was found that the tests were using interfaces compared to the implementation. The tests were changed to match the implementation.

In the compliance test, the implementation of the heartbeat and parameter setting message intervals were different.
The test was changed to match the implementation. Should the specification be updated to match the implementation?

.venv and *.egg-info were added to .gitignore.

Changes

• Change frequency argument of set_pwm function to accept 0 in device_uio to pass integration tests
• Change test_ifmux_can_messages in test_integration_all_messages to use correct channel selection function and CANSpeed enumeration to allow execution of the test.
• Change test_timing_requirements in test_official_manual_compliance to match heartbeat and parameter setting intervals in the device_uio implementation and interface for task_info object to allow execution of the test.
• Add extra set_external_relay lines to 05_can_communication.py script to enable testing using the mux to join the CAN channels.
• Add .venv and *.egg-info to .gitignore

How was this tested?

The pytest tests were executed and the script was run. The debug outputs showed that the tests and script were working as expected.