update include statements to use new pluginlib and class_loader headers

[mikaelarguedas]

Disclaimer: This in an automated PR, if it is not relevant on this branch, apologies for the inconveniance, feel free close it.

---

pluginlib and class_loader headers have been refactored and renamed. The previous headers .h have been deprecated in favor of their .hpp equivalent. The new headers are available on all active ROS distributions and the deprecated ones will be removed in a future version of ROS (likely ROS-N).

This PR migrates the include statements to use the non-deprecated ones and should compile for any active ROS distribution starting with Indigo
The migration was done by running the scripts pluginlib_headers_migration.py and class_loader_headers_update.py on this repository.
Note: this will not work for Jade

[v4hn]

should not be merged yet, because the upstream changes are not rolled out yet.

[mikaelarguedas]

Upstream changes have been released and synced on all active distros. From what it looks like the only CI that is failing is Jade, that will not see a new release as it's been EOL for a while now.

[v4hn]

hae? I see that now, sorry.
But then why did the same fail for moveit kinetic/lunar?

I approve this being merged into a new kinetic-devel branch.
Releases should be done from that branch too then.

[mikaelarguedas]

At a glance that ci is based on ros-base docker images that have not been rebuilt yet (last build was 24 days ago, before the last sync).
This is a known problem of the official ros images that is being investigated osrf/docker_images#112.

In the meantime I recommend running an apt upgrade before performing builds in CI to ensure to have up-to-date packages in your.

[mikaelarguedas]

I approve this being merged into a new kinetic-devel branch.
Releases should be done from that branch too then.

👍
I targeted the branches used in the lunar distribution file to open these PRs. In the case of this repo, it was jade-devel.
It could also be merged in this branch if you don't want to branch out and assume that people still building Jade are either building the distro from source or using the jade debs (in the former case headers are updated and match,, in the latter nothing changes as no new deb will be created)