[Terminology] Introduction to several important Azurite issue labels

[tseyanghub]

• alignment
  Explaination from Azurite: Alignment between Azurite with Azure Storage production
  My understanding from browing issues: This kind of issues are about inconsistency between Azurite and Azure Storage production. There are several inconsistencies as follows:

1. Azurite cannot support methods or functions exactly like Azure Real Service.
   Example:
   For the QueueSasBuilder class in Azure, the doc says that it is fine not to set “StartsOn”. However, Azurite will throw out the exception called GetAuthorizationFailure if StartsOn is empty. The code link.
2. The error info of Azurite is different from Azure Real Service.
   Example:
   The error returned in Azurite is inconsistent with the one in Azure when using queue service SAS to create a queue. Link. The funny thing is that developers do not handle them for a long time and it is considered as stale now.

• featureparity
  Explaination from Azurite: Tracking issues for catching up feature parity
  My understanding from browing issues: This kind of issues are about features that exist in Azure but is not supported in Azurite.
  Example: Azurite does not support to emulate Azure File Share for local development. link

• enhancement
  Explaination from Azurite: New feature or request
  My understanding from browing issues: This kind of issues are similar to ones labelled with featureparity. However, This kind of issues may contain issues about things like Azurite configuration and table performance improvement, which are not related to inconsistency between Azurite and Real one.
  Example:
  Azurite Configuration enhancement link
  Table Service performance improvement link

[tianyin]

Thanks @tseyanghub ! This actually leads to a nice point that we can study the historical issues in the Azurite repo to understand what went wrong in the past, in addition to the effort of doing testing on the recent versions.