Support more and less sophisticated approaches to read the confirmed trip count
Support more and less sophisticated approaches to read the confirmed trip count

This now supports both the leaderboard branch and the main branches.
If we have computeConfirmed, we use it.
If we don't have it, we just read the number of trips that are unlabeled. Note
that this does not take into account the high confidence label assist trips, so
it is only approximate, and should be handled better once we improve the
accuracy of label assist.

https://github.com/e-mission/e-mission-server/pull/873#issuecomment-1210815339

```
./e-mission-py.bash bin/monitor/check_participant_status.py
storage not configured, falling back to sample, default configuration
URL not formatted, defaulting to "Stage_database"
Connecting to database URL localhost:27017
False    4
Name: user_input, dtype: int64
For test_jun_20: Trip count = 6, location count = 285, first trip = 2016-06-20T08:41:15.856000-07:00, last trip = 2016-06-20T17:12:39.767000-07:00, confirmed_pct (2016-05-25T00:00:00+00:00 -> 2016-06-25T00:00:00+00:00) = exactly 66.67
```

```
./e-mission-py.bash bin/monitor/check_participant_status.py
storage not configured, falling back to sample, default configuration
URL not formatted, defaulting to "Stage_database"
Connecting to database URL localhost
For test_jun_20: Trip count = 6, location count = 285, first trip = 2016-06-20T08:41:15.856000-07:00, last trip = 2016-06-20T17:12:39.767000-07:00, confirmed_pct  = approximately 0.67
```

shankari/e-mission-server,e-mission/e-mission-server,shankari/e-mission-server,e-mission/e-mission-server,e-mission/e-mission-server,e-mission/e-mission-server,shankari/e-mission-server,shankari/e-mission-server