Split itkHausdorffDistanceImageFilterTest to the corresponding classes unit tests

Description

The classes ``itk::HausdorffDistanceImageFilteranditk::DirectedHausdorffDistanceImageFilter` are tested in the same [`itkHausdorffDistanceImageFilterTest.cxx](itk::https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/Filtering/DistanceMap/test/itkHausdorffDistanceImageFilte

Add a PolyDataIO based on the VTK::IOPDALmodule:

https://github.com/Kitware/VTK/tree/master/IO/PDAL

Steps (a complete example can be found here):

0. Verify that the test suite runs and passes

Following ITK issue 1049 and the corresponding PRs, ITK uses strongly typed enums. The ITK v5 migration guide provides details about the current practice in ITK:
https://github.com/InsightSoftwareConsortium/ITK/blob/master/Documentation/ITK5MigrationGuide.md#strongly-typed-enumerations

This practice should be reflected by the ITK

As reported by @jhlegarreta, the Build, test, package badges' links point to an SVG file across many (all?) remote modules (maybe also in the ITKModuleTemplate). I'd dare to say that this is not really helpful: IMHO they should point to each repository's master branch in the Action tab e.g.:
https://github.com/InsightSoftwareConsortium/ITKIOFDF/actions/workflows/build-test-package.yml?que

Current tests are limited. In order to have a robust module, tests should exercise the class methods, and compare the expected output (i.e. the baseline) to the one produced when running the test.