Provide a way to force Geo node status to refresh if we retrieve status from DB

If we migrate the Geo node status screen to use the internal GeoNodeStatus from !3230 (merged), we lose the ability to see real-time updates and have to wait 1 minute to see if things are okay. I know I've been on customer calls where being able to hit refresh immediately on the page was incredibly useful, and being able to check the state both on the primary and secondary has been valuable. I worry that we lose the ability to see things on the secondary if the database is stale for some reason.

• @to1ne started a discussion: (+1 comment)

  Admin::GeoNodesController#status is still using Geo::NodeStatusService directly. I think it should also get the status from db.