Handle unsupported message type errors in client generator

[Jotheeswaran-Nandagopal]

• [x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

• Updated the client generator to raise a click exception for unsupported datatypes, by validating the message type after getting the metadata.
• Added try-except block to catch the exceptions raised during the creation of multiple clients and for all registered measurements. Also, show warning message about client creation failure and continue client creation for subsequent measurements.

Why should this Pull Request be merged?

• This implementation fixes the following issues,

  • 974

  • 906

What testing has been done?

• Done manual testing
• Existing automation test passed

[github-actions[bot]]

Test Results

    40 files  ±0      40 suites  ±0   49m 54s :stopwatch: - 1m 11s    700 tests ±0     700 :white_check_mark: ±0      0 :zzz: ±0  0 :x: ±0  17 000 runs  ±0  15 930 :white_check_mark: ±0  1 070 :zzz: ±0  0 :x: ±0 

Results for commit 4698bca4. ± Comparison against base commit ebe576e5.

:recycle: This comment has been updated with latest results.

[Jotheeswaran-Nandagopal]

@dixonjoel , @bkeryan I have refactored the code and implemented the requested changes. Please help me reviewing the changes.

[Jothees07]

@bkeryan, I have updated the changes. Kindly, help us reviewing the changes at your earliest convenience.