Handle multi step form with bad step data

[tyaginidhi]

This pull request primarily focuses on the src/web/client/dal/remoteFetchProvider.ts and src/web/client/utilities/commonUtil.ts files. The changes involve the replacement of the NO_CONTENT constant with checks for null or undefined values, the addition of error handling in the preprocessData function, and the inclusion of a new telemetry event.

Here are the key changes:

Refactoring and Error Handling:

• src/web/client/dal/remoteFetchProvider.ts: Replaced checks against NO_CONTENT with isNullOrUndefined checks in the processDataAndCreateFile and preprocessData functions. This change improves the robustness of the code by handling null or undefined values more explicitly. [1] [2]
• src/web/client/dal/remoteFetchProvider.ts: Added error handling in the preprocessData function. In case of an error, an error telemetry event is sent.

Code Simplification:

• src/web/client/dal/remoteFetchProvider.ts: Simplified the code in the createFile function by using the nullish coalescing operator.
• src/web/client/utilities/commonUtil.ts: Removed the NO_CONTENT constant from the import statement and replaced it with checks for undefined values in the getAttributeContent function. [1] [2]

Telemetry Addition:

• src/web/client/telemetry/constants.ts: Added a new telemetry event WEB_EXTENSION_PREPROCESS_DATA_WEBFORM_STEPS_FAILED to track failures in preprocessing data.