[doc] add doc for carefully choosing path template to produce legal c…

…ontainer name, add report issue section in README.md

AssetOptionsBinder.cs

@@ -34,7 +34,8 @@ This is specific to the cloud you are migrating to.
     ${AssetId}       for the Guid of the assetId.
     ${ContainerName} for the container name of the input asset.
     ${AlternateId}   for the alternative id of the input asset, use AssetName if AlternateId is not set.
-e.g., ams-migration-output/${AssetName}/ will upload to a container named 'ams-migration-output' with path beginning with the input asset name.")
+e.g., ams-migration-output/${AssetName}/ will upload to a container named 'ams-migration-output' with path beginning with the input asset name.
+Warning: For custom path template, please ensure that the container name portion (the part of the template that is before the first '/') conforms to legal azure blob container name (see https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata).  In particular, please refrain from using ${AssetName} in the container name portion unless you are sure that the resulting name conforms to legal azure blog container name.")
         {
             Arity = ArgumentArity.ZeroOrOne
         };

README.md

@@ -22,6 +22,10 @@ trademarks or logos is subject to and must follow
 Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
 Any use of third-party trademarks or logos are subject to those third-party's policies.
 
+## Reporting Issues
+
+If you encounter any issues or bugs that you'd like to report, please feel free to open an issue.  For bugs, it would be extremely helpful if you attach the output log file from the tool.
+
 ## Overview
 A command line tool to migrate your data from Azure Media Services.
 This tool helps you to migrate your media data from Azure Media Services (AMS).