Fix task.resolved_action callbacks

[s-hertel]

SUMMARY

Noticed while looking at the related fix to not use this attribute for module_defaults in #81909.

Not sure if there is a better way to set this - it feels a bit redundant to load the plugin context additional times.

ISSUE TYPE

• Bugfix Pull Request

[s-hertel]

@nitzmahone Not sure if you have any thoughts on this, but after thinking about this in conjunction with module_defaults, I'm wondering if the resolved_action attribute is just rather unhelpful for collections that use a common action plugin.

For example, say vyos_mod1 and vyos_mod2 are redirected to the action plugin vyos. To prevent module_defaults for vyos_mod1 clobbering the default args for vyos_mod2 or vice versa, they can add the action_plugin directive for modules in the runtime.yml.

If these tasks run while using a callback that displays the resolved_action, they will all be displayed as the vyos action, rather than the potentially-more-helpful module name. This is only sort of similar to the module_defaults issue (basically unusable feature vs bad readability). Could I adjust the resolved_action to reflect the resolved module in this case, or is that overloading the task attr/the module metadata magic?

[s-hertel]

I didn't actually realize this also fixes #81905, but it does so I added tests and a changelog.