Expose the parameters log_training_metrics and log_validation_loss for object detection and instance segmentation

[bhimar]

Description

Expose the parameters log_training_metrics and log_validation_loss for object detection and instance segmentation

The test runs below use the JOS and azureml-automl-dnn-vision changes for exposing and setting these parameters.

Tests:

Scenario	Run	Notes
OD
individual 'Enable'	run	both params set to 'Enable'
individual 'enable'	run	both params set to 'enable', in HD driver script they appear as 'Enable'
individual 'Disable'	run	both params set to 'Disable
individual 'disable'	run	both params set to 'disable', in HD driver script they appear as 'Disable'
individual don't specify params	run	the params are not specified through SDK, so the MFE defaults are picked up: log_training_metrics == 'Enable' and log_validation_loss == 'Disable as in the HD driver script
Automode	run	both params are not present in the HD script, so they pick up the runtime defaults: log_training_metrics == 'Disable' and log_validation_loss == 'Enable'
IS
individual 'Enable'	run	both params set to 'Enable'
individual 'enable'	run	both params set to 'enable', in HD driver script they appear as 'Enable'
individual 'Disable'	run	both params set to 'Disable
individual 'disable'	run	both params set to 'disable', in HD driver script they appear as 'Disable'
individual don't specify params	run	the params are not specified through SDK, so the MFE defaults are picked up: log_training_metrics == 'Enable' and log_validation_loss == 'Disable as in the HD driver script
Automode	run	both params are not present in the HD script, so they pick up the runtime defaults: log_training_metrics == 'Disable' and log_validation_loss == 'Enable'

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[github-actions]

Thank you for your contribution @bhimar! We will review the pull request and get back to you soon.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-ai-ml

[rdondera-microsoft]

LGTM, thank you for the comprehensive tests. Be sure to get a review from an actual SDK expert too.