Use the `retry_options` already being used for the Salt minion service,
since we're getting failures such as this one:

* https://github.com/myii/salt-formula/runs/2415072504

This is made worse by the fact that GitHub Actions cannot re-run a
single job (at the current time).

## [1.8.3](https://github.com/saltstack-formulas/salt-formula/compare/v1.8.2...v1.8.3) (2021-04-22)

### Continuous Integration

* **kitchen+gitlab:** adjust matrix to add `3003` ([480b7ed](480b7edbfb))
* **vagrant:** add FreeBSD 13.0 [skip ci] ([6316991](6316991334))
* **vagrant:** add Windows 10 pre-salted box [skip ci] ([fd285d8](fd285d8c5b))

### Tests

* **aluminium:** add pillar, tests and verification files for `3003` ([752a1de](752a1dea22))
* **freebsd:** add `map.jinja` verification file (for 13.0) ([10ae613](10ae613cae))

ci(kitchen+gitlab): adjust matrix to add `3003`

* Semi-automated using https://github.com/myii/ssf-formula/pull/318

* Automated using https://github.com/myii/ssf-formula/pull/316

* Semi-automated using https://github.com/myii/ssf-formula/pull/313
* Add Window 10 map verification file

## [1.8.2](https://github.com/saltstack-formulas/salt-formula/compare/v1.8.1...v1.8.2) (2021-04-09)

### Bug Fixes

* **freebsd:** fix package names [skip ci] ([a30f124](a30f124485))

### Continuous Integration

* **vagrant:** use pre-salted boxes & conditional local settings [skip ci] ([5941618](5941618c6e))

### Tests

* **freebsd-11:** fix `osfinger` in comment [skip ci] ([26f2cc1](26f2cc1ef0))

Right now when you set module_config entries in your pillar data
like this:
salt:
  minion:
    module_config:
      smtp.from: 'Kali Salt <admins+salt@kali.org>'
      smtp.to: 'Kali Admins <admins+salt@kali.org>'
      smtp.host: localhost
      smtp.subject: 'Results of salt actions on'
      smtp.fields: id,fun

On each run, you will always a different ordering of the various
fields in the minion configuration file, leading to spurious restart
of the minion and admin annoyance:

          ID: salt-minion
    Function: file.recurse
        Name: /etc/salt/minion.d
      Result: True
     Comment: Recursively updated /etc/salt/minion.d
     Started: 13:39:25.689775
    Duration: 874.318 ms
     Changes:
              ----------
              /etc/salt/minion.d/f_defaults.conf:
                  ----------
                  diff:
                      ---
                      +++
                      @@ -930,10 +930,10 @@
                       # A dict for the test module:
                       #test.baz: {spam: sausage, cheese: bread}
                       #
                      +smtp.fields: id,fun
                      +smtp.from: Kali Salt <admins+salt@kali.org>
                       smtp.to: Kali Admins <admins+salt@kali.org>
                      -smtp.fields: id,fun
                       smtp.host: localhost
                      -smtp.from: Kali Salt <admins+salt@kali.org>
                       smtp.subject: Results of salt actions on

With the change here, this bad behaviour is gone...

* Automated using https://github.com/myii/ssf-formula/pull/311

* Automated using https://github.com/myii/ssf-formula/pull/310

Resolves issues introduced in 24ebbb4e0c.

## [1.8.1](https://github.com/saltstack-formulas/salt-formula/compare/v1.8.0...v1.8.1) (2021-03-30)

### Bug Fixes

* **freebsd:** update to provide support for most recent versions ([24ebbb4](24ebbb4e0c))
* **openbsd:** update to provide support for most recent versions ([61201de](61201de8c6))
* **osfamilymap:** use `whoami` for Windows `rootuser` ([69d5981](69d598138e)), closes [#495](https://github.com/saltstack-formulas/salt-formula/issues/495)

### Code Refactoring

* **retry_options:** provide options from defaults/pillar ([bbd7286](bbd7286240))

### Continuous Integration

* enable Vagrant-based testing using GitHub Actions ([163c77f](163c77fcee))
* **kitchen+ci:** use latest pre-salted images (after CVE) [skip ci] ([cfefcc8](cfefcc83c0))
* **windows:** use `kitchen.windows.yml` ([c6043fb](c6043fbc9d))

### Documentation

* **readme:** add `Testing with Vagrant` section ([ef1bc02](ef1bc02a86))

### Tests

* update for new platforms (inc. using `system` library) ([e6bcdc1](e6bcdc1b4d))
* **_mapdata:** add Arch Linux verification file ([e31a56e](e31a56e7a3))
* add Windows map verification files ([e0afe89](e0afe89f24))
* standardise use of `share` suite & `_mapdata` state [skip ci] ([9816f47](9816f473c5))

ci: enable Vagrant-based testing using GitHub Actions

Fix #495

* Semi-automated using https://github.com/myii/ssf-formula/pull/304

* Automated using https://github.com/myii/ssf-formula/pull/302

* Automated using https://github.com/myii/ssf-formula/pull/299

ci(windows): use `kitchen.windows.yml`

* Automated using https://github.com/myii/ssf-formula/pull/297

# [1.8.0](https://github.com/saltstack-formulas/salt-formula/compare/v1.7.5...v1.8.0) (2021-03-03)

### Features

* allow selecting alternate salt package repositories ([8742ab3](8742ab30bb))

### Tests

* **debian+ubuntu:** update `pkgrepo` to use `https` instead of `http` ([e94a8c9](e94a8c9dce))

feat: allow selecting alternate salt package repositories

```
$ GREP_SED="\(pkgrepo: deb http\):" \
  && grep -rl "${GREP_SED}" test/integration/v* \
     | xargs sed -i -e "/${GREP_SED}/s//\1s:/"
```

Make the upstream salt package repository selectable, thus allowing the
use of archived salt versions (hosted in
https://archive.repo.saltproject.io), as well as custom salt versions
hosted in alternate repositories.

## [1.7.5](https://github.com/saltstack-formulas/salt-formula/compare/v1.7.4...v1.7.5) (2021-03-02)

### Bug Fixes

* revert to using `is mapping` in Jinja2 ([a89fb3f](a89fb3f4aa))

### Continuous Integration

* **gemfile+lock:** use `ssf` customised `kitchen-docker` repo [skip ci] ([25fea89](25fea89238))
* **kitchen+gitlab-ci:** use latest pre-salted images [skip ci] ([fb9901e](fb9901e3ac))
* **pre-commit:** update hook for `rubocop` [skip ci] ([a874a76](a874a76967))

fix: revert to using `is mapping` in Jinja2

* CVE-2021-25283 enables Jinja2 safe mode, which breaks use of
  `'dict' in x.__class__.__name__` workaround
* Workaround no longer needed as CentOS 6 is EOL

* Automated using https://github.com/myii/ssf-formula/pull/296

* Automated using https://github.com/myii/ssf-formula/pull/295

* Automated using https://github.com/myii/ssf-formula/pull/294

* Automated using https://github.com/myii/ssf-formula/pull/293

* Automated using https://github.com/myii/ssf-formula/pull/292

* Automated using https://github.com/myii/ssf-formula/pull/290

## [1.7.4](https://github.com/saltstack-formulas/salt-formula/compare/v1.7.3...v1.7.4) (2021-01-29)

### Bug Fixes

* **osfamilymap:** update openSUSE `pkgrepo` URLs ([48f8da0](48f8da0357))
* **pkgrepo/suse/install:** avoid managing repo if it already exists ([d5320a3](d5320a35ed)), closes [/github.com/saltstack/salt/blob/45cc49daed1618dbe89e1f012128c8dcab00b356/salt/modules/zypperpkg.py#L1262-L1265](45cc49daed/salt/modules/zypperpkg.py/issues/L1262-L1265)

### Continuous Integration

* **kitchen+gitlab:** update for new pre-salted images ([a9413e8](a9413e8c29))

### Tests

* **tumbleweed:** add map verification files ([6aeaa5a](6aeaa5ac94))

ci(kitchen+gitlab): update for new pre-salted images

Use ugly `zypper lr --uri` hack to get around failure if the `base_url`
already exists under a different name:

```
      ID: salt-pkgrepo-install-saltstack-suse
Function: pkgrepo.managed
    Name: systemsmanagement_saltstack_products
  Result: False
 Comment: Failed to configure repo 'systemsmanagement_saltstack_products':
          Repository 'systemsmanagement_saltstack_products' already exists as 'systemsmanagement_saltstack'.
 Started: 09:28:39.154054
Duration: 2760.727 ms
```

Upstream code:

* 45cc49daed/salt/modules/zypperpkg.py (L1262-L1265)

* Semi-automated using https://github.com/myii/ssf-formula/pull/288

## [1.7.3](https://github.com/saltstack-formulas/salt-formula/compare/v1.7.2...v1.7.3) (2020-12-23)

### Tests

* **_mapdata:** generate verification files ([da6d150](da6d1509fd))
* **map:** verify `map.jinja` dump using `_mapdata` state ([d2404d5](d2404d5175))