[DryIoc] Update default container rules.

[Dudulle]

Description of Change

Update default container rules in Prism.DryIoc.Wpf and Prism.DryIoc.Forms.

Type registration from DryIocContainerExtension has become inconsistent between WPF and Xamarin since commit 9b82533.
This commit makes both platforms behave the same way again.

Moving the mentioned changes to the default container rules makes type registration from the container and container extension behave consistently and allows to override the behavior of the container extension.

Bugs Fixed

Fixes a bug equivalent to #1304 on WPF platform.

API Changes

None

Behavioral Changes

By default, the container will resolve types using the constructor with the most resolvable arguments.
The container extension will use default rules for registration (no change for WPF).

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[dnfclas]

All CLA requirements met.

[dansiegel]

Generally LGTM, if we are updating the default Rules, go ahead and clean up the ContainerExtenstion for Forms.

[Dudulle]

@dansiegel do you mean this file? (WPF did not have those parameters, which is why I mentioned the behavior was currently inconsistent)
Or did I miss something else?

[dansiegel]

sorry was looking at this on my phone earlier... thought that was the WPF one... LGTM

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.