Add funding information to package.json and gemspec files

[andrew]

User description

Description

Added funding_uri to both gemspecs and funding links to package.json to match with FUNDING.yml.

Motivation and Context

To help increase visibility using the bundle fund and npm fund commands.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

enhancement

---

Description

• Added funding_uri to the selenium-devtools and selenium-webdriver gemspec files to enhance visibility for funding options.
• Updated package.json to include a funding section with links to GitHub Sponsors and OpenCollective, supporting the npm fund command.

---

Changes walkthrough 📝

Relevant files

Enhancement

selenium-devtools.gemspec Add funding URI to selenium-devtools gemspec                          rb/selenium-devtools.gemspec Added funding_uri to gemspec metadata. Enhances visibility for funding options. +2/-1      selenium-webdriver.gemspec Add funding URI to selenium-webdriver gemspec                        rb/selenium-webdriver.gemspec Added funding_uri to gemspec metadata. Enhances visibility for funding options. +2/-1      package.json Add funding information to package.json                                    javascript/node/selenium-webdriver/package.json Added funding section with GitHub and OpenCollective links. Supports npm fund command for funding visibility. +11/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Validation Needed Verify that the GitHub sponsor URL is correct and active Configuration Check Verify that both funding URLs (GitHub and OpenCollective) are valid and point to the correct pages

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.

[VietND96]

Thank you, @andrew!