Fix actions loading

[chrisradek]

This PR fixes an issue that occurs when explicitly enabling/disabling action destinations.

A very small handful of action destinations have a different plugin name than their creation name. Amplitude is one of these.
Our current remote loader implementation only takes into account the plugin's name and not the creation name when deciding whether to load the destination.

That means there are 2 scenarios where loading Amplitude would not do the expected thing.

1. analytics.load(writeKey, { integrations: { All: false, "Actions Amplitude": true }})
   With this scenario, all destinations are disabled by default and only if one is explicitly enabled will it be loaded. In this specific example, the plugin name is Amplitude (Actions) despite the integration (creationName) being Actions Amplitude. This mismatch caused the plugin to fail to load.

2. analytics.load(writeKey, { integrations: { "Actions Amplitude": false }})
   With this scenario, the destination is explicitly disabled. However without these changes users would have had to specify Amplitude (Actions) instead.

[x] I've included a changeset (psst. run yarn changeset. Read about changesets here).

[changeset-bot]

🦋 Changeset detected

Latest commit: bfa66ff

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@segment/analytics-next	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pooyaj]

💯