change swagger-js wrapActions to js object

[Axiloom]

Specifying for plugins to be chain loaded was causing an issue where a specific wrapActions (plugins/swagger-js) was not able to be set because the. scope of the variable was wrong.

Description

Changing the swagger-js wrapActions to use a js object instead of the original key/value pair, which was preventing the wrapActions from being set

Motivation and Context

Solves the problem of not being able to chain load plugins

Fixes #7730

How Has This Been Tested?

I haven't been able to test and will provider a comment in the issue

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

Not entirely sure about this

[char0n]

This is technically an invalid usage of wrapActions interface. The code here creates unsupported nested wrapActions object:

wrapAction: {
  configsWrapActions: {
    loaded: ...implementation...
  }
}

[char0n]

Thanks for contributing! I've made a change to the PR which I explained in CR and issue comment.