Overhaul site information page

[williamjallen]

The site information page /sites/<id> is currently somewhat broken, and does not present much useful information. This PR is the first of several planned as part of a revitalization of the CDash site feature. The entire UI was rebuilt with DaisyUI based on information provided via the GraphQL API. Further improvements remain to be made, including:

• The "claim site" feature should be moved to this page
• Site information should be editable directly from this page
• Aggregate time per project, current site location, and build status information should be added

Closes #1126

Related to #1984

New UI:

[josephsnyder]

Overall, I like the page update but I have one nit to pick. A single submission from a new site created four History system updates all with identical information at the same time (down to the second). Is there a way to group them by time of submission or something else?

[williamjallen]

@josephsnyder Do you see four results in the database? You can run select * from siteinformation where siteid = ?; to check.

I think the page should display whatever the server sends back, even if that means that duplicate information is displayed. Instead, I think we should fix the root of the problem, which is the bad deduplication. I noticed some odd preexisting behavior related to site information deduplication that I plan to work on in a separate PR. Thoughts?

[josephsnyder]

@williamjallen,

@josephsnyder Do you see four results in the database? You can run select * from siteinformation where siteid = ?; to check.

Correct. There are 4 entries for this particular siteid so it looks like a deduplication problem.

[williamjallen]

@josephsnyder I'll add some logic to ignore duplicates for the moment, until I can resolve the deduplication issue.

[josephsnyder]

Also, @williamjallen, I just found that one of the test sites returns mostRecentInformation: null and the loading spiral isn't going away. I'm not sure how often we'll get a null case but it might be worth accounting for:

[williamjallen]

@josephsnyder Good idea. It should theoretically be impossible to have a site without information in a production system, but it certainly can't hurt to handle the case if it does happen for whatever reason.

[josephsnyder]

Looks great and all my comments were addressed!