Potential fix for code scanning alert no. 15: Uncontrolled data used in path expression

[Shubhranshu153]

Potential fix for https://github.com/runfinch/finch-daemon/security/code-scanning/15

To fix the problem, the code must ensure that any directory passed to os.RemoveAll (via the variable dir) is not controlled by the user in an unsafe manner. The preferred fix is to make sure that dir is always located within a known temporary or controlled directory owned by the service, and to validate that dir is not allowed to escape this safe root. This can be accomplished using filepath.Abs() (to resolve symlinks and produce an absolute path), and filepath.HasPrefix() or a similar strategy to check containment. Alternatively, if dir is expected to be only ever a temp directory created by the service in this code path, then we should enforce or verify that expectation; otherwise, the directory should not be deleted, or the operation should be aborted. The required edits are to check, right before os.RemoveAll(dir), that dir is indeed a child of a safe temporary directory root (for example, the system temp directory given by os.TempDir()), and, if not, abort the operation.

This may require importing appropriate path/strings utilities, such as path/filepath and strings, if not already imported (though in this case, they are).

Suggested fixes powered by Copilot Autofix. Review carefully before merging.