100% compatible tslint checks

[Jicmou]

If you have a PrimeNG PRO Support subscription please post your issue at;

https://pro.primefaces.org

where our team will respond within 4 business hours.

If you do not have a PrimeNG PRO Support subscription, fill-in the report below. Please note that
your issue will be added to the waiting list of community issues and will be reviewed on a first-come first-serve basis, as a result, the support team is unable to guarantee a specific schedule on when it will be reviewed. Thank you for your understanding.

I'm submitting a ... (check one with "x")

[X] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Plunkr Case (Bug Reports)

No need for a Plunkr to reproduce. Just a terminal.

Current behavior

while in Project directory, run in terminal:

node_modules/.bin/tslint --project tslint.json | wc -l

Could not find implementations for the following rules specified in the configuration:
    no-access-missing-member
    templates-use-public
    invoke-injectable
Try upgrading TSLint and/or ensuring that you have all necessary custom rules installed.
If TSLint was recently upgraded, you may have old rules configured which need to be cleaned up.
        
   13536

Which means: "Return the number of lines of the output of tslint"

Expected behavior

1. tslint should return 0 error from master.
2. tslint should be part of CI workflow, so no single PR is able to merge if carrying tslint errors.

Indeed, there's no point having a tslint.json file in the project, if we're not using it.

What is the motivation / use case for changing the behavior?

Several actions can be taken to fix this issue.

1. Some tslint rules need to be adapted to the develepment practices: (e.g: "component-selector", "no-inferrable-types", ...)
2. Some rules need to stay and the code must be cleaned up.
3. tslint must be a step in the travis build, so that if any error is present in the PR, the build fails, forcing the developer to fix the error, in order to see his PR merged.

I am ready to open a couple of PR related to this topic, if that's a step the maintainers of this repo are willing to take ;)

Please tell us about your environment:

tslint@5.7.0
IDE: vscode
package manager: npm
OS: macOS 10.13.4

• Angular version: 5.X

Angular agnostic, as this issue concerns this repo only

• PrimeNG version: 5.X

6.0.0-SNAPSHOT. Last commit: 10325e1

• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

No Browser needed.

• Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript 2.4.2

• Node (for AoT issues): node --version =