fix: check correct ETS table for stop state last updated

[lemald]

Summary of changes

Asana Ticket: 🍎 Look into /stops updating too frequently in v3 API /status endpoint

Upon examination, it turned out that the Stop state is implemented a bit differently from most of the other states, in that the process that actually use-es State.Server and tracks the state in an ETS table isn't State.Stop but State.Stop.Cache. The State.Metadata.last_updates/1 function returns the result of DateTime.utc_now/0 if no timestamp is found in ETS, so because we were looking for the last updated time of the wrong module we were always getting the current time.

[github-actions]

Coverage of commit 18ec2e1

Summary coverage rate:
  lines......: 89.1% (4231 of 4750 lines)
  functions..: 70.2% (2284 of 3255 functions)
  branches...: no data found

Files changed coverage rate:
                                                                        |Lines       |Functions  |Branches    
  Filename                                                              |Rate     Num|Rate    Num|Rate     Num
  ============================================================================================================
  apps/state/lib/state/metadata.ex                                      |90.0%     30|90.9%    11|    -      0

Download coverage report

[github-actions]

Coverage of commit 135ef18

Summary coverage rate:
  lines......: 89.1% (4232 of 4751 lines)
  functions..: 70.2% (2285 of 3257 functions)
  branches...: no data found

Files changed coverage rate:
                                                                        |Lines       |Functions  |Branches    
  Filename                                                              |Rate     Num|Rate    Num|Rate     Num
  ============================================================================================================
  apps/state/lib/state/metadata.ex                                      |90.0%     30|90.9%    11|    -      0

Download coverage report