fix: only list asset models for the requested engine group

[Kuruyia]

What does this PR do ?

This fixes a regression introduced in #362 on the listAssets (and by extension, searchAssets) actions of the device-manager/models controller that wasn't correctly taking into account the requested engine group and was returning the models for every group instead.

The problematic Elasticsearch query has been fixed.

Other changes

Two new asset models, Room and StreetLamp, were added in the test application, respectively to the air_quality and public_lighting engine groups.

Tests were added to avoid this regression in the future.

Boyscout

To avoid an inconsistent list of asset models, the asset models are now reset before each test of the asset-model.test.ts file.

[afondard]

You could define the same measures as in the Room asset model from iot-platform

Suggested change

	measures: [
	{
	name: "temperature",
	type: "temperature",
	},
	{
	name: "humidity",
	type: "humidity",
	},
	],
	measures: [
	{
	name: "temperature",
	type: "temperature",
	},
	{
	name: "humidity",
	type: "humidity",
	},
	{
	name: "co2",
	type: "co2",
	},
	{
	name: "illuminance",
	type: "illuminance",
	},
	],

[afondard]

As the position is a constant it's better in the metadatas (cf iot-platform)

Suggested change

	measures: [
	{
	name: "position",
	type: "position",
	},
	],
	metadataMappings: {
	street: { type: "keyword" },
	},
	measures: [
	{
	name: "brightness",
	type: "brightness",
	},
	{
	name: "powerConsumption",
	type: "powerConsumption",
	},
	],
	metadataMappings: {
	position: { type: "geo_point" },
	street: { type: "keyword" },
	},