Rename singleton to avoid 3rd party plugin conflict

[allendav]

Changes proposed in this Pull Request:

Issue: #1375
Fixes #1375

Description: Renames the singleton to avoid conflicts with the https://wordpress.org/plugins/woo-stripe-payment/ plugin

Testing instructions

• Install and activate this branch
• Install and activate https://wordpress.org/plugins/woo-stripe-payment/ Edit: You must use a release < 3.2.8
• Ensure they are both able to be activated simultaneously without error

---

• Make sure your changes respect WordPress' coding standards.
• Did you make changes, or create a new .js file? If Gruntfile.js exists in the repo, make sure to run grunt.

(remove me)

• Did I add a title? A descriptive, yet concise, title.
• How can this code break?
• What are we doing to make sure this code doesn't break?

[reykjalin]

I wanted to take a look at this PR and try to test it, but it seems I don't have any issues with enabling the woo-stripe-payment plugin since I can't go through the Stripe Connect authentication; I don't have confirmed bank details associated with my account, which is required to complete the authentication.

I didn't find a way to enter the publishable and secret keys manually either. If there's a way to do that I'd be happy to take a look at this again.

FWIW the changes look good, I just can't test them 🙂

cc @v18 @dechov

[allendav]

@reykjalin - did you try testing with a version older than 3.2.8? https://wordpress.org/plugins/woo-stripe-payment/#developers

[reykjalin]

@allendav ah, I did not! And I just noticed following your comment that they already changed the name of their function as well.

In any case, using a version older than 3.2.8 causes a fatal error on master and no error on this branch. LGTM!