Fix Java spotless line-wrapping and Python import order

Apply the exact reflows spotless computed (javadoc wrapping in the e2e test
and ProviderTokenArgs, and the provider.getToken call in the dispatcher), and
move BearerTokenProvider to its correct alphabetical position in the python
package exports after the getBearerToken rename.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: SteveSandersonMS

java/src/main/java/com/github/copilot/RpcHandlerDispatcher.java

@@ -328,7 +328,8 @@ private void handleProviderTokenGetToken(JsonRpcClient rpc, String requestId, Js
                     return;
                 }
 
-                CompletableFuture<String> tokenFuture = provider.getToken(new ProviderTokenArgs(providerName, sessionId));
+                CompletableFuture<String> tokenFuture = provider
+                        .getToken(new ProviderTokenArgs(providerName, sessionId));
                 if (tokenFuture == null) {
                     rpc.sendErrorResponse(requestIdLong, -32603,
                             "Bearer-token provider returned null future for provider " + providerName);

java/src/main/java/com/github/copilot/rpc/ProviderTokenArgs.java

@@ -51,8 +51,8 @@ public String getProviderName() {
     /**
      * Gets the id of the session that triggered this token request.
      * <p>
-     * A client-level shared callback registered for many sessions can use this
-     * to resolve the owning session and scope token acquisition or caching per
+     * A client-level shared callback registered for many sessions can use this to
+     * resolve the owning session and scope token acquisition or caching per
      * session.
      *
      * @return the session id

java/src/test/java/com/github/copilot/ByokBearerTokenProviderE2ETest.java

@@ -43,9 +43,9 @@
 
 /**
  * End-to-end coverage for the experimental BYOK bearer-token-provider surface
- * ({@code BearerTokenProvider} on a provider config). The callback stays entirely on
- * the SDK/client side: the SDK keeps it off the wire, sends only the
- * {@code hasBearerTokenProvider} flag, and the runtime calls back over the
+ * ({@code BearerTokenProvider} on a provider config). The callback stays
+ * entirely on the SDK/client side: the SDK keeps it off the wire, sends only
+ * the {@code hasBearerTokenProvider} flag, and the runtime calls back over the
  * session-scoped {@code providerToken.getToken} RPC before each outbound model
  * request.
  */

python/copilot/__init__.py

@@ -86,6 +86,7 @@
     AutoModeSwitchHandler,
     AutoModeSwitchRequest,
     AutoModeSwitchResponse,
+    BearerTokenProvider,
     CommandContext,
     CommandDefinition,
     CopilotSession,
@@ -100,7 +101,6 @@
     ExitPlanModeHandler,
     ExitPlanModeRequest,
     ExitPlanModeResult,
-    BearerTokenProvider,
     InfiniteSessionConfig,
     InputOptions,
     LargeToolOutputConfig,