Change character validation in tag key to align with server behavior

[EmmaZhu]

Thanks for contribution! Please go through following checklist before sending PR.

PR Branch Destination

• For Azurite V3, please send PR to main branch.
• For legacy Azurite V2, please send PR to legacy-dev branch.

Always Add Test Cases

Make sure test cases are added to cover the code change.

Add Change Log

Add change log for the code change in Upcoming Release section in ChangeLog.md.

Development Guideline

Please go to CONTRIBUTION.md for steps about setting up development environment and recommended Visual Studio Code extensions.

[SamPersson]

It seems the failing test is correct: key111==value1 should still result in http status 400

If tag names are regular SQL identifiers, they may be present without escaping; if they contain any special characters, they must be delimited with double quotes (e.g. "TagName" = 'TagValue').

(https://learn.microsoft.com/en-us/rest/api/storageservices/specifying-conditional-headers-for-blob-service-operations#tags-predicate-syntax)

So I guess it needs separate validation for double quote delimited tag keys, and only then allow +-./:=