Add dockerfiles for testing before release

[kunaltyagi]

• Adds a dockerfile for building PCL on debian:testing
• Adds a dockerfile for building PCL and perception_pcl on kinetic and melodic flavors of ROS
• Adds a CI to perform some tasks of the release with a manual trigger
• Kinetic perception_pcl is broken since 1.10, and can't be targeted by PCL
• Tested manually for melodic

Offshoots of this PR:

• PR Changes in preparation for PCL 1.11 ros-perception/perception_pcl#273 to address changes in downstream project to handle change of pointers

TODO after this PR:

• Test CI

[kunaltyagi]

Need help testing the dockerfiles

[jspricke]

Note that perception_pcl is in Debian (testing), so you could go with apt source -b ros-perception-pcl

[kunaltyagi]

Azure is running out of disk space for compiling PCL on debian:testing

[kunaltyagi]

PR opened (ros-perception/perception_pcl#273) to make sure downstream target pcl_ros works after the smart pointer API break.

All images have been verified manually (not on CI) before the API break

EDIT:
Since the mentioned PR has been merged, Dockerfile has been tested after the break with melodic

[kunaltyagi]

Should I remove the commented code? The plan was to test it in this PR, but my account's CI doesn't have enough space to build PCL

Once merged, we can test it on PCL's CI with increased memory quota. Speaking of which @taketwo could you please contact Azure to increase CI space just a bit more so Windows doesn't OOM out randomly.

[taketwo]

could you please contact Azure to increase CI space just a bit more so Windows doesn't OOM out randomly

They said they have to technical possibility to increase the space.

[kunaltyagi]

They said they have to

Did you mean "They said they have no" instead?

[taketwo]

Yep, no technical possibility, sorry. To quote their answer:

We do not have the ability to increase the free disk space limit on hosted machines. Everyone in free tier and paid tier get the same free disk space.

[kunaltyagi]

Got it. In which case, I guess we see what happens after this gets reviewed, merged and a new pipeline is created.

[taketwo]

Do we need to generate source tarball manually? One can always download a tarball for a tag/release from GitHub.

[kunaltyagi]

Yes. That's sadly needed because the GitHub interface isn't quite the same as the GitHub task on Azure CI. I tried with not uploading a source, but then the release didn't have anything

[kunaltyagi]

Merging to start testing with PCL's pipeline instead of mine