fix(api): peek pipette bug fixes

[caila-marashaj]

Overview

On testing the peek pipette on a robot, there are two bugs:

• The peek pipette was getting loaded by serial number correctly as an em_pipette, but the shared-data file getting loaded in was that of the regular 8 channel pipettes
• The custom default_max_speed was getting overwritten by ot3api::set_system_constraints_for_plunger_acceleration

This pr contains fixes for both of these that have been tested on the robot.

Changelog

• remove update_constraints_for_emulsifying_pipette, instead just place a check for the high speed pipettes inside set_system_constraints_for_plunger_acceleration
• add necessary EIGHT_CHANNEL_EM types so the correct shared-data file gets loaded in

Test Plan

• Load a peek pipette onto the robot using cache_instruments
• Aspirate, make sure the speed on the move request on the CAN bus, after conversion, is 90 mm/sec
• Dispense make sure the speed on the move request on the CAN bus, after conversion, is 90 mm/sec
• During both of these, make sure there are no bind_sensor_output_requests directed to the peek pipette

[sfoster1]

Looks good but let's change the name of the param