The catalog is compiled for every example, so testing the same resource
in a single example is faster.

Group spec expectations in a single example

Allow `DefaultDependencies` to be specified as a `Boolean` in
the `[Unit]` section of a templated unit or dropin file.

e.g.

```puppet
systemd::manage_unit{'my.service':
  ensure     => present,
  unit_entry => {
    'DefaultDependencies' => false,
  },
}
```

https://www.freedesktop.org/software/systemd/man/systemd.unit.html#DefaultDependencies=

The timer directives for unit files is now complete for options
present in the man page of systemd-253.

For example:

```puppet
systemd::manage_unit{'my.timer':
  ensure => present,
  unit_entry => {
    'Description' => 'my timer',
  },
  timer_entry => {
    'Calendar' => 'daily',
    'AccuracySecs' => '1 hour',
  },
}
```

Previously only the 'Calendar' directive was available and this
patch also includes a bug fix for that.

Previously

```
systemd::manage_dropin{'my.timer':
  ensure => present,
  unit => 'myunit.service',
  timer_entry => {
    'Calendar' => ['','daily'],
  },
}
```
with an empty resetting first `''` element was not permitted and now it is..

Addition of timer directives to manage_unit and manage_dropin

Allow DefaultDependencies to be set in [Unit] section

The path directives for unit files is now complete for options present in the man page
of systemd-253.

The parameter `path_entry` can now be specified for `systemd::manage_unit` or
`systemd::manage_dropin`.

For example:

```puppet
systemd::manage_unit{'etc-passwd.path':
  ensure     => present,
  unit_entry => {
    'Description' => 'Monitor /etc/passwd',
  },
  path_entry => {
    'PathChanged' => '/etc/passwd',
    'Unit'        => 'etc-passwd-updates.service',
  },
}
```

or

```puppet
systemd::manage_dropin{'trigger-limit.conf':
  ensure     => present,
  unit       => 'etc-passwd.path',
  path_entry => {
    'TriggerLimitBurst' => 100,
  },
}
```

https://www.freedesktop.org/software/systemd/man/systemd.path.html

While

```puppet
systemd::manage_dropin{'custom.conf':
  ensure => present,
  unit   => 'my.service',
  timer_entry => {
   'Calendar' => 'Daily'
  },
}
```
was failing the error message gave incorrect information.

The catalog is compiled for every example, so testing the same resource
in a single example is faster.

Increase inifile dependency upper version to < 7.0.0

Addition of path directives to manage_unit/dropin

Allow a SyslogIdentifier to be specified as:

```puppet
systemd::manage_unit{'roger.service':
  ensure => present,
  unit_entry => {
    'Description' => 'My Service',
  }
  service_entry => {
    'ExecStart'        => '/usr/bin/doit',
    'SyslogIdentifier' => 'logdoit',
  }
```

`systemd::manage_dropin` can be used similarly.

https://www.freedesktop.org/software/systemd/man/systemd.exec.html#SyslogIdentifier=

Allow KillMode and KillSignal to be specified
to `systemd::manage_unit` and `systemd::manage_dropin`

Allow SyslogIdentifier, KillMode and KillSignal to [service] section

Refactor the unit template to:
* Reduce code duplication
* Make it easier to add new sections to the unit file.

Addition of LimitCOR to `[service]` section of
`systemd::manage_unit` and `systemd::manage_dropin`

Added as penance for giving a wrong guess twice to someone how
to do this. Always confuse me since while:

`systemctl show sshd.service -t LimitCORESoft` has a value it cannot be
set as I understand it.

* https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%20Properties

Drop Puppet 6 support

Allow LimitCORE in [Service] for manage_unit/dropin

Refactor unit template

modulesync 6.0.0

Release 5.0.0