STYLE: Increase tests style consistency

[jhlegarreta]

Increase tests style consistency:

• Use the itkNameOfTestExecutableMacro to get the test name and prevent
  the the test from crashing when argv[0] is null.
• Use the ITK testing macros when calling filter update methods to reduce
  boilerplate code.
• Increase consistency in the missing argument check message.
• Use EXIT_SUCCESS and EXIT_FAILURE to return from tests on
  success/failure.
• Use the ITK_EXERCISE_BASIC_OBJECT_METHODS macro instead of explicitly
  calling the Print method.

Take advantage of the commit to:

• Remove the argument check when no input parameters are required.
• Define the required types within the test body.
• Define the required types once the input argument check has passed.
• Remove duplicate calls to filter updates.
• Remove unused expected exception cases.
• Only enclose within the ITK_TRY_EXPECT_NO_EXCEPTION macro the filter
  update calls that may throw exceptions.
• Remove some unnecessary printed messages.
• Remove unnecessary comment lines devoid of relevant content.

PR Checklist

• No API changes were made (or the changes have been approved)
• No major design changes were made (or the changes have been approved)

[jhlegarreta]

Cross-referencing PR #564.

A few notes:

• Using the itk::ImageWrite method is out of the scope of this PR.
• Increasing the consistency for the argc < vs. argc != check can be done in a separate PR (its scope is broader than this PR and requires agreement on the ITK SW Guide).
• Increasing the consistency in the constant declaration (e.g. pixel dimensionality) is let for a separate PR (its scope is broader than this PR).
• I did not add the test ending printed messages. That can be done in a separate PR (its scope is broader than this PR and requires agreement on the ITK SW Guide).
• I did not check all Update calls. That can be done in a separate PR (its scope is broader than this PR).
• I did not check for the input argument name style in the parameter number check. That can be done in a separate PR (its scope is broader than this PR and requires agreement on the ITK SW Guide).
• I did not check for comment message styles (except for a few exceptions). That can be done in a separate PR.
• Modules/IO/JPEG2000/test/itkJPEG2000ImageIORegionOfInterest.cxx and Modules/IO/NIFTI/test/itkExtractSlice.cxx should be appended with the Test label IMHO. Can be done/better in a separate PR.

[tbirdso]

Test macro standardization looks great! One typo to fix for CI.

[dzenanz]

Awesome!