Revert 397 and add Deprecation warning instead

[jtroussard]

Semantic version mistake was made when releasing 1.3.1, the Linkedin compliance fix which was removed from the code base, api breaking change, did not trigger a main version release increment. e.g. 1.4 instead of 1.3.1.

This PR reverts the Linkedin compliance hook removal, and instead adds a deprecation warning. Can remove next major version release. Return Linkedin example file to original state as well as bringing back unit tests.

Updates HISTORY and AUTHOR file.

[coveralls]

Coverage increased (+0.3%) to 90.637% when pulling 16a3473 on revert-397 into b3decdb on master.

[JonathanHuot]

Can you rebase from 1.3.1 tag ?
That way we're not introducing other breaking changes already in master.

[jtroussard]

@JonathanHuot we good now?

[JonathanHuot]

For hotfix, I think we should merge into master only after the release of v1.3.2.

So basically, I will suggest to raise PR to merge your changes into the release-1.3.2 branch (just created now based on v1.3.1 tag).

Once your changes merged and reviewed, we can push tag v1.3.2 and that will trigger the release to pypi.

Once released and happy, we can merge release-1.3.2 into master to target 1.4.x.

[JonathanHuot]

Closed as no time to fix backward the version to maintain version semantic.