Instead of using a single _deviceDisplayInfo() function to configure
its delegates, load per-service files that define their own delegate
UIs.

The issue with the _deviceDisplayInfo() is that it causes binding
updates to all delegates whenever any of the displayed delegate values
change. The per-service delegate solution also allows custom list
items for individual services, instead of requiring all services to
use a similar delegate UI.

All delegates should have the same appearance as before, except for
the Inverter delegate, which has been fixed to only show the power for
the currently active phase.

Issue #1338

The _deviceDisplayInfo() in DeviceListPage is problematic as it causes
binding updates to all delegates whenever any of the displayed
delegate values change.

Instead of using this single gigantic function to configure delegates,
load per-service QML files that define their own delegate UIs. This
improvement also means that custom list items can be provided for
individual services, instead of requiring all services to use a
similar delegate UI.

All delegates should have the same appearance as before, except for
the Inverter delegate, which has been fixed to only show the power for
the currently active phase.

Issue #1338

The _deviceDisplayInfo() in DeviceListPage is problematic as it causes
binding updates to all delegates whenever any of the displayed
delegate values change.

Instead of using this single gigantic function to configure delegates,
load per-service QML files that define their own delegate UIs. This
improvement also means that custom list items can be provided for
individual services, instead of requiring all services to use a
similar delegate UI.

All delegates should have the same appearance as before, except for
the Inverter delegate, which has been fixed to only show the power for
the currently active phase.

Issue #1338

The _deviceDisplayInfo() in DeviceListPage is problematic as it causes
binding updates to all delegates whenever any of the displayed
delegate values change.

Instead of using this single gigantic function to configure delegates,
load per-service QML files that define their own delegate UIs. This
improvement also means that custom list items can be provided for
individual services, instead of requiring all services to use a
similar delegate UI.

All delegates should have the same appearance as before, except for
the Inverter delegate, which has been fixed to only show the power for
the currently active phase.

Issue #1338

The _deviceDisplayInfo() in DeviceListPage is problematic as it causes
binding updates to all delegates whenever any of the displayed
delegate values change.

Instead of using this single gigantic function to configure delegates,
load per-service QML files that define their own delegate UIs. This
improvement also means that custom list items can be provided for
individual services, instead of requiring all services to use a
similar delegate UI.

All delegates should have the same appearance as before, except for
the Inverter delegate, which has been fixed to only show the power for
the currently active phase.

Issue #1338

QuantityObject provides QObject-based access to a quantity value.
QuantityObjectModel provides a model of QuantityObject values; it
filters out objects without valid values.

This allows ListQuantityGroup and its derived types to specify their
models without creating a JavaScript array that directly refers each
quantity value. Otherwise, whenever a quantity value is updated, the
entire array is rebuilt, which in turn causes the QuantityRow repeater
to rebuild its delegates.

Part of #1338

…Group

This improves the performance of QuantityRow in updating its displayed
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity value changes.

The updates affect the following types and their uses:
- ListQuantityGroup
- ...

Replace all uses of ListTextGroup with ListQuantityGroup, except where
the text is static, or in PageTankShape where the list is dynamically
generated from an array.

[WIP]
Still to do:
- verify all changes
- update uses of quantityModel from device list delegates
- add filter option to QuantityObjectModel to disable filtering in table mode
- rebase on top of SolarInputListPage PR
- update uses of QuantityRow outside of ListQuantityGroup (e.g. battery list page)
- update PagePowerDebug

Part of #1338

Use QuantityTable as ListTextGroup will be obsoleted.

Use BackendConnection.uidPrefix() to load the page in mock mode.

Part of #1338

Use QuantityTable as ListTextGroup will be obsoleted.

Use BackendConnection.uidPrefix() to load the page in mock mode.

Part of #1338

Use QuantityTable as ListTextGroup will be obsoleted.

Use BackendConnection.uidPrefix() to load the page in mock mode.

Part of #1338

QuantityObject provides QObject-based access to a quantity value.
QuantityObjectModel provides a model of QuantityObject values, and
is able to filter out items that do not have valid values.

This allows ListQuantityGroup and its derived types to specify their
models without creating a JavaScript array that directly refers each
quantity value. Otherwise, whenever a quantity value is updated, the
entire array is rebuilt, which in turn causes the QuantityRow repeater
to rebuild its delegates.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid. (In the DC input and solar input
Overview drilldowns, where invalid values should still be shown due to
the table-like display, set QuantityObjectModel.NoFilter instead of
tableMode=true to preserve the table format.)

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid. (In the DC input and solar input
Overview drilldowns, where invalid values should still be shown due to
the table-like display, set QuantityObjectModel.NoFilter instead of
tableMode=true to preserve the table format.)

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid. (In the DC input and solar input
Overview drilldowns, where invalid values should still be shown due to
the table-like display, set QuantityObjectModel.NoFilter instead of
tableMode=true to preserve the table format.)

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

QuantityObject provides QObject-based access to a quantity value.
QuantityObjectModel provides a model of QuantityObject values, and
is able to filter out items that do not have valid values.

This allows ListQuantityGroup and its derived types to specify their
models without creating a JavaScript array that directly refers each
quantity value. Otherwise, whenever a quantity value is updated, the
entire array is rebuilt, which in turn causes the QuantityRow repeater
to rebuild its delegates.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

QuantityObject provides QObject-based access to a quantity value.
QuantityObjectModel provides a model of QuantityObject values, and
is able to filter out items that do not have valid values.

This allows ListQuantityGroup and its derived types to specify their
models without creating a JavaScript array that directly refers each
quantity value. Otherwise, whenever a quantity value is updated, the
entire array is rebuilt, which in turn causes the QuantityRow repeater
to rebuild its delegates.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

QuantityObject provides QObject-based access to a quantity value.
QuantityObjectModel provides a model of QuantityObject values, and
is able to filter out items that do not have valid values.

This allows ListQuantityGroup and its derived types to specify their
models without creating a JavaScript array that directly refers each
quantity value. Otherwise, whenever a quantity value is updated, the
entire array is rebuilt, which in turn causes the QuantityRow repeater
to rebuild its delegates.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338

Change QuantityRow's model type to QuantityObjectModel, so that the
model cannot be specified as an array of real values, and update the
codebase accordingly so that it always uses QuantityObject with
QuantityObjectModel instead of an array-based model in all cases where
multiple quantities are displayed.

This greatly improves the performance of QuantityRow in updating its
values, as the Repeater no longer rebuilds its delegates whenever a
single quantity changes in the model.

Also, since QuantityObjectModel is able to filter out invalid values,
it is not necessary to create and show separate models depending on
whether particular values are valid.

The updates affect the following types and their uses:
- QuantityRow
- ListQuantityGroup
- ListQuantityGroupNavigation

Also remove ListTextGroup and replace its uses with ListQuantityGroup,
as ListTextGroup was being used to show text alongside number values,
and that can now easily be done with ListQuantityGroup as a
QuantityObject value can be a string if the unit is Units_None.

Part of #1338