Allow TelemetryInitializer properties to be overridden by user

[daveta]

Fix issue that VA encountered.
Allow users to override telemetry that's logged from the initializer.

[coveralls]

Pull Request Test Coverage Report for Build 50132

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.04%) to 74.599%

---

Totals
Change from base Build 49945:	0.04%
Covered Lines:	4003
Relevant Lines:	5366

---

💛 - Coveralls

[cleemullins]

@daveta Does this need to be updated on the JS side as well?

[daveta]

Small update here:

• I've got an outstanding query with Ben about functionality of nodejs.
• I believe nodejs at the moment has a bug where it's not placing the bot properties (so no chance of collision!)
• Based on implementation in nodejs, no chance of user overrides throwing an exception (like C#).
• HOWEVER, depending on the nodejs Application Insights hook we are using, it may not be possible to override the bot properties. It all boils down to the order in which the hook gets called. So, until (a) the bug gets fixed and (b) we can understand the order of invocation in nodejs, let's sit on this for a bit. If a user cannot override, then for parity, we shouldn't "fix" this bug..

[cleemullins]

@daveta Any update on this?

[daveta]

Ok, so it appears the hook that we initialize the bot properties (now fixed) should be be overridable given restify calls it first.

It should behave the same way on both C# and node.

[cleemullins]

Per @daveta, "Yes, in js it's already there - you can consider this a js equivalence".

Merging.