Fix conflict between illuminance and illuminance_lux

[kiall]

On certain devices, e.g. GZCGQ01LM, 9290012607, 9290019758, TERNCY-PP01 etc, both
cfg.sensor_illuminance and cfg.sensor_illuminance_lux are applied. As both of these
had the same object_id, only one would show in Home Assistant. Oddly, a mix of both
would apply - e.g. I would get the illuminance value, with the illuminance_lux unit
of 'lx'.

The new test, without the change to add _lux, would produce the following output:

 FAIL  test/homeassistant.test.js (7.952s)
  ● HomeAssistant extension › Should not have duplicate type/object_ids in a mapping

    expect(received).toHaveLength(expected)

    Expected length: 0
    Received length: 4
    Received array:  ["GZCGQ01LM", "9290012607", "9290019758", "TERNCY-PP01"]

      51 |         });
      52 |
    > 53 |         expect(duplicated).toHaveLength(0);
         |                            ^
      54 |     });
      55 |
      56 |     it('Should discover devices', async () => {

      at Object.it (test/homeassistant.test.js:53:28)

[branch-switcher]

Hello @kiall. The base branch of this pull request has been updated to the dev branch. Please revisit the changes and make sure that there are no conflicts with the new base branch. Thank you for your contributions.

[Koenkk]

Big thanks!