reimplemented eva telemetry with new data

[ivanvuong]

set new thresholds for heart rate, temperature and oxygen consumption based on https://github.com/SUITS-Techteam/TSS_2024/blob/main/SUITS_TelemetryValueRanges.pdf

changed screen one to only hold values of heart rate (BMP) , temperature (F) , and oxygen consumption (PSI/MIN)

created new interface types for all:

 interface BiometricData {
    batt_time_left: number;
    co2_production: number;
    coolant_gas_pressure: number;
    coolant_liquid_pressure: number;
    coolant_m1: number;
    fan_pri_rpm: number;
    fan_sec_rpm: number;
    heart_rate: number;
    helmet_pressure_co2: number;
    oxy_consumption: number;
    oxy_pri_pressure: number;
    oxy_pri_storage: number;
    oxy_sec_pressure: number;
    oxy_sec_storage: number;
    oxy_time_left: number;
    scrubber_a_co2_storage: number;
    scrubber_b_co2_storage: number;
    suit_pressure_co2: number;
    suit_pressure_other: number;
    suit_pressure_oxy: number;
    suit_pressure_total: number;
    temperature: number;
  }

created a call to /tss/telemetry which set values and returned those values based on each eva

generalized the default and return values for use within screen two regarding the values that were unused for screen 1

currently the values are constant because there is no data source, but the values are being accessed correctly from each eva, _in which batt_timeleft is an example value where there is a clear difference in data between eva1 and eva2, which will not be shown in screen1 and is currently taken out

"telemetry": {
    "eva1": {
      "heart_rate": 90.0,
      "temperature": 70.0
      "oxy_consumption": 0.0,
      "batt_time_left": 5077.148926,
    },
    "eva2": {
      "heart_rate": 90.0,
      "temperature": 70.0
      "oxy_consumption": 0.0,
      "batt_time_left": 3384.893799,
    },
}

will revise if design changes are needed, more values need to be displayed on screen1 or implementing the constant updating of values needs to be added