[ENHANCEMENT] Update version of saltstack used for testing

Currently, GitHub actions that inherit from this project to do watchmaker-related testing tasks are testing with SaltStack 3006.10 (per):

 C:\\salt\\salt-call.exe --versions-report
Salt Version:
          Salt: 3006.10
 
Python Version:
        Python: 3.10.16 (heads/main:c504d17, Mar  6 2025, 02:25:38) [MSC v.1943 64 bit (AMD64)]
 
Dependency Versions:
          cffi: 1.14.6
      cherrypy: 18.6.1
  cryptography: 42.0.5
      dateutil: 2.8.1
     docker-py: Not Installed
         gitdb: 4.0.7
     gitpython: 3.1.41
        Jinja2: 3.1.6
       libgit2: Not Installed
  looseversion: 1.0.2
      M2Crypto: Not Installed
          Mako: Not Installed
       msgpack: 1.0.2
  msgpack-pure: Not Installed
  mysql-python: Not Installed
     packaging: 22.0
     pycparser: 2.21
      pycrypto: Not Installed
  pycryptodome: 3.19.1
        pygit2: Not Installed
  python-gnupg: 0.4.8
        PyYAML: 6.0.1
         PyZMQ: 25.0.2
        relenv: 0.18.1
         smmap: 4.0.0
       timelib: 0.2.4
       Tornado: 4.5.3
           ZMQ: 4.3.4
 
System Versions:
          dist: mingw64_nt-10.0-26100 3.6.6 
        locale: utf-8
       machine: AMD64
       release: 2025Server
        system: Windows
       version: 2025Server 10.0.26100 SP0 Multiprocessor Free

The above is taken from a recent, failing CI test in the notepad-plusplus-formula project.

It would probably be A Good Idea™ to upgrade to the latest point-release of SaltStack 3007 (currently .13) to better reflect the versions actively being used for current deployment activities.

Start with the reusable GitHub Actions workflows in this repository and compare their SaltStack setup with the failing notepad-plusplus-formula CI run linked in the issue. Identify where the testing version is selected and update it to SaltStack 3007.13, then verify that the referenced workflow reports the intended version and completes successfully.