[onesignal]Update onesignal.rb to include optional organization_id

[brandon-carpenter]

🔑 adds optional, organization_id, paramater to onesignal.rb

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

This change adds the Onesignal organization_id as an optional parameter. Presently, when new Onesignal applications are created, they are created without being assigned to an organization. This allows end users to specify an organization_id if desired. Apps created under an organization will delegate the Onesignal org-level-admins to that application. Org-level-admins are unable to view/modify apps not within the organization.

No issue has been created. Please let me know if you'd like an issue created for this PR.

Description

The additional parameter was added inline with the other parameters in onesignal.rb. Payload has been updated along with self.available_options, and self.example_code.

Both bundle exec rubocop -a and bundle exec rspec as referenced here were ran following the changes.

Testing Steps

bundle exec onesignal was ran with a Fastfile containing the necessary parameters including organization_id. This resulted in a new application being created within Onesignal under the provided organization_id. This allowed org-level-admins to view the newly created onesignal application. Additionally, the changes were ran on an app update successfully, and on an app without the organization_id provided. On the latter, the app was created without being assigned to an organization. The changes will also update an application that was created outside of an organization and will move it under the provided organization.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[brandon-carpenter]

@googlebot I signed it!

[joshdholtz]

This looks good! Just a few small requests 😊

[brandon-carpenter]

Updated with your suggestions. Thanks!

[joshdholtz]

Looks great! Thank you so much for the contribution ❤

[fastlane-bot]

Hey @brandon-carpenter 👋

Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉
The code change now lives in the master branch, however it wasn't released to RubyGems yet.
We usually ship about once a week, and your PR will be included in the next one.

Please let us know if this change requires an immediate release by adding a comment here 👍
We'll notify you once we shipped a new release with your changes 🚀

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.170.0 🚀