Make Client ready for archieving

[wlkrm]

v.2.0.0-rc4 before the TypeDictonary merge #431 was the last stable version before the client started to break.
Known sources of the accumulated issues:

• TypeDictonary (Type dictionary #431)
• Dynamic Jobs (Dynamic reading of objects  #129) (Included ModelChanged Eventhandling. Fixed update of nodes after reconnection. #368)

Issues to fix forch achiving:

• "The server certificate is different from the EndpointDescription" errors and crashes #868
• Client not working with UaServer (.Net) #698
• Logging of BadNoMatch is not correct #816
• Reconnection Logic
• ResultManagement in GMS Crashes possibly related to dynamic ResultManagement nodes #788
• [MV]Unable to parse ResultDataType for Machinery  #497
• Error with reduant BrowePath #747
• Memory Leak/ Magic number in buildCustomDataTypes #570
• Client does not build type map, if connection instability during initial start #380

[wlkrm]

@GoetzGoerisch @ainglessi please add details, other known issues, etc.
@mdornaus @Kantiran91 please describe, which commits after v.2.0.0-rc4 / the ModelChangedEvent are needed.

[ainglessi]

Just checked #868, still happens with the latest SampleServer and Client images.

[wlkrm]

@ainglessi, does #868 work with v.2.0.0-rc4 ?

[ainglessi]

@ainglessi, does #868 work with v.2.0.0-rc4 ?

Looks like it, no crashes within half an hour so far. Trying sample-server:develop with dashboard-opcua-client:v2.0.0-rc4.

[wlkrm]

I suggest that we roll back to v.2.0.0-rc4. Add the important bugfixes from development branch and replace the
type dictionary by manual decoding of the ResultType.

[GoetzGoerisch]

So not just reverting #431?

I prepared a branch: https://github.com/umati/Dashboard-OPCUA-Client/tree/revert/431

[Kantiran91]

@wlkrm I think the Feature with the version is interesting. The rest im not sure.