refactor(app-canary): monitor only a single GUID

[cgraham-rs]

Refactor includes:

• Only monitoring a single GUID
• Removing pandas since we no longer need to store a dataset of multiple content results
• Displaying monitoring results in a callout instead of a table since we are no longer collecting multiple content results
• Displaying any errors in a callout instead of shoving them into the results (previously directly into the results table). This makes the error much more consumable and functions as providing feedback about malformed/invalid GUID, or GUID you don't have access to for whatever reason
• Improved output when you don't have permissions to view the logs for the monitored content, which should only happen if you are a viewer
• Significant refactoring of the overall code to reduce duplication and complexity

This is deployed on our internal Connect server: https://dogfood.team.pct.posit.it/connect/#/apps/54e4557b-812d-4f70-afc6-9f2e5022a179/environment

Fixes https://github.com/posit-dev/connect/issues/32394
Fixes https://github.com/posit-dev/connect/issues/32404

Tests

• No CANARY_GUID env var set
  • If scheduled, DOES NOT send an email
• Invalid GUID
  • If scheduled, sends an email
• Valid GUID for content you are a owner of
• Valid GUID for content you are a collaborator of
• Valid GUID for content you are a viewer of
• Valid GUID for content you do not have access to (not in ACL, etc.)
  • In the above setup, where the monitored content passing validation, if scheduled, DOES NOT send an email
• Valid GUID, content is published but fails validation
  • If scheduled, sends an email

Required env var not set.

Invalid GUID set

Valid GUID, owner of content, content passes validation

Valid GUID, collaborator of content, content passes validation

Valid GUID, viewer of content, content passes validation

Vaid GUID, no permission to content

Valid GUID, owner of content, content fails validation

[toph-allen]

This was a somewhat fast review. The code looks understandable. I published the bundle and pointed it at a broken application, and got the expected email. Looks good. And managing only a single variable is much easier.

[toph-allen]

In the final version maybe we wanna tell them where to click to re-render? I mean, maybe they know, but maybe a screenshot of the button. ¯_(ツ)_/¯

[cgraham-rs]

Do you have a strong feeling about this? I am assuming that if someone has published something to Connect they know how to re-render? I'm noting that the Posit Connect UI button tooltip is Refresh Report and I'm not quickly finding anything in the Posit Connect User Guide that seems to document that process. Regardless, there could be a language/wording mismatch here.

[cgraham-rs]

I will change this wording in a follow-on PR.