[dotnet] Unify the link .net api docs

[nvborisenko]

User description

Description

Changed link to .net api docs to follow the pattern of all other bindings.

Motivation and Context

To be unified.

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

---

PR Type

documentation

---

Description

• Updated the .NET API documentation link in the Selenium Clients and WebDriver Language Bindings section to ensure consistency with other language bindings.
• The new link points to the official Selenium GitHub Pages for .NET API documentation.

---

Changes walkthrough 📝

	Relevant files
Documentation	selenium-clients-and-webdriver-bindings.html Update .NET API documentation link for consistency              website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html Updated the .NET API documentation link to a new URL. Ensured consistency with other language bindings documentation links. +1/-1

---

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

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	2cb8b09

[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

⚡ No major issues detected

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Add security attribute to external link to prevent potential vulnerabilities Consider adding a rel="noopener" attribute to the external link for improved security. This prevents the new page from accessing the window.opener property and helps protect against potential vulnerabilities. website_and_docs/layouts/partials/selenium-clients-and-webdriver-bindings.html [39] -<a href="https://seleniumhq.github.io/selenium/docs/api/dotnet/index.html" class="card-link"> +<a href="https://seleniumhq.github.io/selenium/docs/api/dotnet/index.html" class="card-link" rel="noopener"> Apply this suggestion Suggestion importance[1-10]: 8 Why: Adding the rel="noopener" attribute is a good security practice for external links, as it prevents the new page from accessing the window.opener property, reducing the risk of certain types of attacks. This suggestion is relevant and improves the security of the code.	8

💡 Need additional feedback ? start a PR chat