Making secrets non-required, adding ref-docs

[KarishmaGhiya]

Making secrets non-required, adding ref-docs:

• Making all the secrets non-required and adding ref-docs to assist user for create methods
• Log Analytics - moved 3 parameters that were only for Basic Auth

Others:

• Re-enabled Eventhub tests
• Fixed recordings and param for app insights - replacing query param with a space character isntead of nbsp chars
• Added Changelog

[chradek]

So, you explained to me offline that the sensitive fields are optional because the same interfaces are used both as input and output to/from the service, and the service will never fill in those fields.

@xirzec had commented on the API view that a better experience would be to keep the sensitive fields as required when sending them to the service, but omit them entirely from the output interface. I do agree that this would be an improvement over making the fields always be optional.

It would make sense for these fields to be optional if they were part of a patch operation, but that doesn't appear to be the case here.

Separately, it looks like some tests may need to be re-recorded for the CI to pass.

[KarishmaGhiya]

@chradek Yes I could either make separate interfaces or add in ref docs for the user. @xirzec and I had synced up off line to discuss this.

[chradek]

It's probably worth a note that the library is also now GA 😄