[java] Migrate PageFactory code to be self-contained

[shs96c]

This change deprecates the existing classes, but delegates the implementations to the copies made in the pagefactory package. This means that a later PR can be made which removes the original classes in support once we're ready.

[selenium-ci]

Thank you, @shs96c for this code suggestion.

The support packages contain example code that many users find helpful, but they do not necessarily represent
the best practices for using Selenium, and the Selenium team is not currently merging changes to them.

After reviewing the change, unless it is a critical fix or a feature that is needed for Selenium
to work, we will likely close the PR.

We actively encourage people to add the wrapper and helper code that makes sense for them to their own frameworks.
If you have any questions, please contact us

[shs96c]

We can make this a java_export to make this its own maven package. When we're ready to remove PageFactory from the main support package, we can then remove this as a dependency of support and we'll be done. At that point, we can extract the whole directory to a separate project, or just keep it around.

[mk868]

Can we also address this issue #14474 before publishing this change?
The transition to the .pagefactory. package will require some changes in the users' code anyway, so they could adapt their code to the changes related to #14474 .

Motivation: https://openjdk.org/jeps/500

What do you think?

[diemol]

@mk868, the idea is to move it to a different package when we release Selenium 5 because we aren't going to work more on this code, so we want to move it to a different place so people notice it. We are also considering ways to offer a path that allows people to move out of this pattern.