fix: Ignore modem state when getting position from MM

[nicolatimeus]

Note: We are using the Conventional Commits convention for our pull request titles. Please take a look at the PR title format document for the supported types and scopes.

Brief description of the PR. [e.g. Added null check on object to avoid NullPointerException]

The ModemManager position provider currently tries to get the location only from modems that are in the MM_MODEM_STATE_CONNECTED or MM_MODEM_STATE_REGISTERED state. This prevents to be able to get the location at least in the following cases:

• Modem GPS is enabled in Kura web UI but IPv4 and IPv6 status is set to disabled
• The modem is enabled for wan but it is not registered to a cellular network (e.g. the cellular antenna is not connected or cellular signal level is low)

This PR removes the filtering based on modem state to decouple the ability to get the location information from the state of the cellular connection.

[mattdibi]

Tested on DG1014

Enabled GPS mode "managed GPS" via ESF UI resulting in:

root@dynagate-10-14:/home/guest# mmcli -m 0 --location-status
  ------------------------
  Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb
           |      enabled: gps-raw, gps-nmea
           |      signals: no
  ------------------------
  GPS      | refresh rate: 30 seconds

root@dynagate-10-14:/home/guest# mmcli -m 0 --location-get
  ----------------
  GPS |      nmea: $GPGSA,[REDACTED]
      |            $GPRMC,[REDACTED]
      |            $GPGSV,[REDACTED]
      |            $GPGSV,[REDACTED]
      |            $GPGSV,[REDACTED]
      |            $GPGSV,[REDACTED]
      |            $GPVTG,[REDACTED]
      |            $GPGGA,[REDACTED]
      |       utc: 152158.00
      | longitude: [REDACTED]
      |  latitude: [REDACTED]
      |  altitude: [REDACTED]

Once enabled PositionService using modemManager provider I can correctly query position via Rest API:

curl -k -u admin:eurotech https:/172.16.0.1/services/position/v1/position | jq .
{
  "longitude": [REDACTED],
  "latitude": [REDACTED],
  "altitude": [REDACTED],
  "speed": 0.0,
  "track": 260.1,
  "gnssType": [
    "Gps"
  ]
}

During all of this the modem connection was disabled:

---

Before this PR, the same call would result in:

curl -k -u admin:eurotech https:/172.16.0.1/services/position/v1/position
{"message":"Service unavailable. Position is not locked."}%