Add configuration drift checker to bash init scripts

[apatel762]

the approach would be something like

• go to repo
• git fetch
• check if origin/master is ahead of master
  • see https://unix.stackexchange.com/a/503548

if so, warn the user to git pull and re-apply the playbook config

could make this into a systemd unit that runs in the background, but not sure if notifications would work (e.g. via notify-send - https://old.reddit.com/r/linux/comments/ea2qo/my_bash_scripts_just_got_so_much_cooler_i_just/c16j1zc/)

• can use --wait to make the notification sticky
• can use --urgency=low as well, just because

[apatel762]

https://wiki.archlinux.org/title/Desktop_notifications#Bash

Some documentation about scripting desktop notifications in bash. Need a way of reliably getting the user id and username for the user that we are installing our systemd service for, or else the notifications won't work

[apatel762]

not sure how this would work actually, because I would need my ssh keys to be loaded for the git fetch to even work