Deserializer didn't handle non-success responses in Modular MPG

[MaryGao]

This is similar to unbranded one, but we would focus on the Azure scope because this behavior introduced breakings between HLC and Modular.

In Modular we only deserialize the success responses and for other responses we would throw as general RestError. So that we temporality ignore the error model generation here.

export async function _getApplicationDeserialize(
  result: PathUncheckedResponse,
): Promise<BatchApplication> {
  const expectedStatuses = ["200"];
  if (!expectedStatuses.includes(result.status)) {
    throw createRestError(result);
  }

  return batchApplicationDeserializer(result.body);
}

But in HLC if default responses or non-success responses are specified we would deserialize to correct response models(see client and core code).

In this issue we need to decide if we would accept this breaking or handle these non-success responses for Azure SDK.

[qiaozha]

Also blocked by #2943