UT new logic

[mrpalide]

Fixes: #2

Changes:

• remove old monthly model
• remove old data once a day. Delete old data as default more than 7 days, but this value could change by --store-data-cutoff flag
• add new flag --store-data-path for path of save daily data, default value is /var/lib/skywire-ut/daily-data
• save last day data to json file, whole of db, as YYYY-MM-DD-uptime-data.json
• decided to return old data as endpoint or store/upload in storage

Screenshots:

How to test:

• run uptime-tracker by README.md manual
• run visor and use local UT
• wait 5 minutes, check endpoint and db
• stop UT, change create_at value of record to yesterday by update daily_uptime_histories set created_at = current_date - 1
• add api.dailyRoutine(logger) to line 153 of api.go file, build and run UT again
• check endpoint, db and store data path for daily data json file there

[jdknives]

If possible, I would like the routine to look like this:

oldestEntry := dbClient.Limit(1).Order("created_at asc")Find(&entry)
from := oldestEntry.createdAt.Format("2006-01-02")
to := time.Now().Add(0, 0 , -(storeCutoffDate))


if (from < to) {
for from; from < to; from.Add(0, 0, 1) {
  dbClient.Limit(1).Where("date == from").FInd(&exportDate)
  exportUptimeDayToStoreIfNotExist(exportDate)
  dbClient.Delete(&exportDae)

}
}

This is just some leetcode to I am sure it needs to be adapted to work properly. But this way we have a few advantages:

1. We always run the routine even if the uptime tracker gets restarted frequently, because we dont rely on the date variable that stored in memory
2. We always back up data even if its older than the store-cutoff-date and dont delete any data without backing up

[jdknives]

Looks good to me. Will do a round of integration testing and then merge if it works. 👍