Fixes #2979 Update 3rd party components to latest

[rwmcintosh]

Fixes #2979

Description

Updates and code changes to accommodate

Type of change

Please mark relevant options with an x in the brackets.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires documentation changes (link at least one user or developer documentation issue):
• Algorithm update - updates algorithm documentation/questions/answers etc.
• Other (please describe):

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Integration tests
• Unit tests
• Manual tests
• No tests required

Reviewer checklist

Mark everything that needs to be checked before merging the PR.

• Check if the code is well documented
• Check if the behavior is what is expected
• Check if the code is well tested
• Check if the code is readable and well formatted
• Additional checks (document below if any)
• Check if documentation update issue(s) are created if the option This change requires a documentation update above is selected

Screenshots (if appropriate):

Questions (if appropriate):

[rwmcintosh]

Not sure how this broke, but I found that some compiler generated classes were registered more than once breaking this scanning convention.

[rwmcintosh]

There is a transitive update to Castle Core involved here.

[Yuri05]

12.1.0.0 or 12.1.0 ?

[rwmcintosh]

I think you define all 3 digits. That's what we had for local builds of 11.3 -> 11.3.0.0

[rwmcintosh]

That's where it makes a difference.

[msevestre]

Boom