Fix manage_file_capabilities

[b3n4kh]

SUMMARY

Fixes a bug where manage_file_capabilities is true and $::vault::package_name is custom name (not 'vault')

TESTS/SPECS

I would like to add a spec test for this, but I would need to host a repository with a different package name. If anyone has a suggestions on how to mock that?
Rest would be smth like:

        context 'when installed from package repository with managed_capability' do
          let(:params) do
            {
              install_method: 'repo',
              package_name: 'vault-private',
              package_ensure: 'installed',
              manage_file_capabilities: true
            }
          end

          it { is_expected.to contain_package('vault') }
          it { is_expected.to contain_file_capability('vault_binary_capability') }

[jsok]

There shouldn't be any need to setup a real package repository to write a spec for this.
See

puppet-vault/spec/classes/vault_spec.rb

Lines 204 to 226 in dcf58c1

	context 'when installed from package repository' do
	let(:params) do
	{
	install_method: 'repo',
	package_name: 'vault',
	package_ensure: 'installed'
	}
	end
	it { is_expected.to contain_package('vault') }
	it { is_expected.not_to contain_file_capability('vault_binary_capability') }
	context 'when managing file capabilities' do
	let(:params) do
	super().merge(
	manage_file_capabilities: true,
	)
	end
	it { is_expected.to contain_file_capability('vault_binary_capability') }
	it { is_expected.to contain_package('vault').that_notifies(['File_capability[vault_binary_capability]']) }
	end
	end

for how it's currently done, it should only require a small modification to verify this change.