ci(kitchen): use fail2ban.ng in state_top

[myii]

PR progress checklist (to be filled in by reviewers)

• Changes to documentation are appropriate (or tick if not required)
• Changes to tests are appropriate (or tick if not required)
• Reviews completed

---

What type of PR is this?

Primary type

• [build] Changes related to the build system
• [chore] Changes to the build process or auxiliary tools and libraries such as documentation generation
• [ci] Changes to the continuous integration configuration
• [feat] A new feature
• [fix] A bug fix
• [perf] A code change that improves performance
• [refactor] A code change that neither fixes a bug nor adds a feature
• [revert] A change used to revert a previous commit
• [style] Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

• [docs] Documentation changes
• [test] Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.

Related issues and/or pull requests

• [FEATURE] Promote 'ng' states #35
• fix(pillar.example): declare ignoreip (whitelist) in jail section (ng) #37

Describe the changes you're proposing

Also contains a bug fix for the ng:lookup.

Pillar / config required to test the proposed changes

Debug log showing how the proposed changes work

Documentation checklist

• Updated the README (e.g. Available states).
• Updated pillar.example.

Testing checklist

• Included in Kitchen (i.e. under state_top).
• Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
• Updated the relevant test pillar.

Additional context

[myii]

Self-merging mainly because the build was failing with the mess of the situation as discussed in #37 and #35. Needs to be done anyway with the plan to promote ng.

[saltstack-formulas-travis]

🎉 This PR is included in version 0.17.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀