Add blog post to explain the breaking changes in Java BiDi

[pujagani]

User description

Related to https://github.com/SeleniumHQ/selenium/pull/13463/files

Thanks for contributing to the Selenium site and documentation! A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines. Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

Add blog post to explain the breaking changes in Java BiDi due to introduction of circular dependency.

Motivation and Context

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

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

---

Type

documentation

---

Description

• Introduced a new blog post titled "Update imports to use BiDi Java", authored by Puja Jagani, explaining the breaking changes in Java BiDi implementation due to circular dependency issues.
• The post details the changes users need to make in their import statements for Selenium versions 4.19 and above.
• It provides a comprehensive explanation of why the change was necessary, including the goal of aligning with W3C BiDi and resolving circular dependency in Bazel.
• Includes before-and-after code snippets to clearly illustrate the changes in import statements.

---

Changes walkthrough

Relevant files

Documentation

bidi-java-breaking-change.md New Blog Post: Explaining Breaking Changes in Java BiDi Implementation website_and_docs/content/blog/2024/bidi-java-breaking-change.md Introduced a new blog post explaining the breaking change in Java BiDi implementation. Detailed the changes required in import statements for Selenium versions 4.19 and above. Explained the rationale behind the change and its impact on users. Provided a before-and-after comparison of import statements. +56/-0

---

✨ PR-Agent usage: Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions