Refactor ChromeDriverFunctionalTest: (#14398)

Refactor ChromeDriverFunctionalTest: Remove redundant permission constants

Removed the CLIPBOARD_READ and CLIPBOARD_WRITE constants from the class level in ChromeDriverFunctionalTest to avoid redundancy. These constants are now defined within the canSetPermission method, reducing unnecessary visibility and improving code cohesion.

This change simplifies maintenance and enhances code clarity without altering existing functionality.

Co-authored-by: Diego Molina <[email protected]>

Author: manuelsblanco

java/test/org/openqa/selenium/chrome/ChromeDriverFunctionalTest.java

@@ -50,9 +50,6 @@
 
 class ChromeDriverFunctionalTest extends JupiterTestBase {
 
-  private final String CLIPBOARD_READ = "clipboard-read";
-  private final String CLIPBOARD_WRITE = "clipboard-write";
-
   @Test
   @NoDriverBeforeTest
   public void builderGeneratesDefaultChromeOptions() {
@@ -109,7 +106,9 @@ void canSetPermission() {
     HasPermissions permissions = (HasPermissions) driver;
 
     driver.get(pages.clicksPage);
+    String CLIPBOARD_READ = "clipboard-read";
     assumeThat(checkPermission(driver, CLIPBOARD_READ)).isEqualTo("prompt");
+    String CLIPBOARD_WRITE = "clipboard-write";
     assumeThat(checkPermission(driver, CLIPBOARD_WRITE)).isEqualTo("granted");
 
     permissions.setPermission(CLIPBOARD_READ, "denied");