[Tables] Refactor error processing mechanism

[YalinLi0312]

The ideal way is able to process Storage tables and Cosmos tables independently.
We will start from test coverage check:

• Check test coverage in error.py:
  • make sure we have recorded tests for both storage and cosmos for every condition check in functions like _validate_tablename_error, _decode_error and _reprocess_error.
  • split processing logic into storage and cosmos when possible.
• Check test coverage in credential combinations:
  Tables now support three credential types and None. Make sure we have recorded tests for three credential types and None on both storage and cosmos. For AzureSasCredential, should having an extra test which including sas_token in endpoint and credential provided at the same time.
• Check test coverage in secondary account host

cc: @annatisch

[github-actions]

Hi @YalinLi0312, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.