Skip the Files Sudo Ignores When Naming a Timestamp Override

The scan for a timestamp option set elsewhere read every file under /etc/sudoers.d, including the ones sudo skips: a name holding a dot, and a name ending in a tilde. This run's own staged file is dot-prefixed, so a leftover from a killed run would be named as an override that sudo never reads.

Author: ptr727

host-setup/linux/install-tools.sh

@@ -1111,8 +1111,10 @@ configure_sudo_timestamp() {
 
     # Another file setting either option is named rather than merged into, since which one wins is the order sudo reads them in and not something this can decide.
     local elsewhere
+    # A name holding a dot or ending in a tilde is one sudo skips, this run's own staged file included, so a setting in it is an override sudo never reads.
     elsewhere=$("${SUDO[@]}" grep -rnsE '^[[:space:]]*Defaults.*timestamp_(type|timeout)' \
-        --exclude="${SUDOERS_FILE##*/}" /etc/sudoers /etc/sudoers.d 2> /dev/null) || elsewhere=""
+        --exclude='*.*' --exclude='*~' --exclude="${SUDOERS_FILE##*/}" \
+        /etc/sudoers /etc/sudoers.d 2> /dev/null) || elsewhere=""
     if [[ -n $elsewhere ]]; then
         warn "A timestamp option is already set elsewhere, and the file sudo reads last wins:"
         local line