Avoid creating .azcopy under HOME if plan/log location is specified elsewhere

[tiverma-msft]

No description provided.

[tiverma-msft]

There are 2 variables here. Log file loc and plan file loc. If one of the locations is specified by an env variable and other is not, we will still create the .azcopy folder to accommodate the file for which user has not provided a location.

Only in the case of both env variables being provided will we skip creating the .azcopy folder.

One of my concerns... something that I'll have to see is if this folder is used for something other than plan and log files. The location of this folder is being shared by cmd.Execute(azcopyAppPathFolder, azcopyLogPathFolder, azcopyJobPlanFolder, 0, jobID) and is then used for common.NewUserOAuthTokenManagerInstance(...)
What is that for? (Adding this to the conversation as a personal note to find out.

[tiverma-msft]

In such a case (when a token json file is being created), the folder .azcopy will be created, and the token will be stored there. The code -DPAPIFilePath: azcopyAppPathFolder in credentialUtil.go decides where the json token will go.
Leaving this as is. i.e as long as the user is not creating tokens, this folder is not created.

[tiverma-msft]

Changes suggested: the OAuth token should be where the plan files are located. This way if the user has provided both plan and log locations, the OAuth will be where plan files are located, and the .azcopy folder will not be created at all. Make changes accordingly