Create github actions workflow to automate JCINK Control Panel deployment

[AJMansfield]

The theme is currently packed into the skinset artifact, with a structure like:

skinset
+ DestinyWeaves_default.xml
+ DestinyWeaves_dark.xml
+ DestinyWeaves_light.xml
+ assets
  + js__flattened_assets.js
  + css__flattened_assets.css
  + images__flattened_assets.png

Deploying the packed theme to JCINK will mean:

• [x] Change skinset name to include a versioning suffix.
  • git describe is our friend
• [x] Verify we've not been blocked in robots.txt, and respect the robots.txt crawl delay.
  • Need to decide on a specific user-agent string to use for this.
  • Current robots.txt specifies Crawl-delay: 10 for User-agent: *.
  • TODO: open a support ticket to request either (a) a smaller crawl delay, or (b) official permission to ignore this crawl delay.
• [x] Log in to JCINK Admin Panel.
  • Need a username/password deploy secret.
  • Are there any 2FA options we could apply here?
• [x] Upload new assets.
  • [x] Create version-suffixed assets folder.
  • [x] Navigate to File Manager.
  • [x] Type assets_<suffix> in "Create New Folder:".
  • [x] Submit form "Submit".
  • [x] Upload assets.
  • Per form label, "A maximum of 10 files per upload is recommended." In practice this doesn't seem to matter, but we should respect this documented limitation regardless and batch things into 10-file batches.
  • [x] Navigate to File Manager > assets_<suffix> subfolder.
  • [x] Select files in "Upload new file(s):".
  • [x] Submit form "Submit".
• [x] Upload new skins. For each skin variant:
  • [x] Navigate to Skin Set Manager.
  • [x] Select skin xml file under "Choose a skin XML file to one-click install a new skin."
  • [x] Submit form "Create new Skin Set".
• [x] Identify versioning suffix for skin-sets we intend to remove / supercede.
• [x] Swap member skin choice. For each skin variant:
  • [x] Select old version in "Where members use skin...".
  • [x] Select new version in "update to use skin...".
  • [x] Submit form "Update member skin choice."
• [x] Delete old skins. For each skin variant:
  • [x] Navigate to Skin Set Manager.
  • [x] Select "remove" for the skin.
  • [x] Press OK on the confirmation dialogue.
  • Do we need to also manually remove associated HTML Template sets?
• [x] Delete old assets.
  • [x] Delete old asset files.
  • [x] Navigate to File Manager > assets_<suffix> subfolder.
  • [x] Check all of the boxes next to the assets.
  • [x] Submit form "Delete".
  • [x] Delete old assets folder.
  • [x] Navigate to File Manager.
  • [x] Check box for assets_<suffix> subfolder.
  • [x] Submit form "Delete".
  • How to handle pagination? File Manager view can theoretically paginate.
  • What if the assets_<suffix> folder doesn't appear on page 1 of the main file manager view?
  • What if some assets don't appear on the page 1 of the subfolder view?
• [x] Log out of JCINK Admin Panel.
  • Proactively void our session token as soon as we're done.

[AJMansfield]

Gonna use python, since it's what I know best -- can implement the AP login/logout as a contextmanager.

[AJMansfield]

JCINK is a very old/jank site, and the admin panel makes heavy use of NN-style Frames.

Maybe it'd be better to try to abstract out and use the underlying API directly, but even figuring out what that API is would be a lot of work.

We'll just use a full headless automation web-browser instead, in the form of Selenium WebDriver.