feat(roll): roll to 1.48 Playwright (#1558)

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

java/versioned_docs/version-stable/ci.mdx

@@ -75,7 +75,7 @@ jobs:
     name: 'Playwright Tests'
     runs-on: ubuntu-latest
     container:
-      image: mcr.microsoft.com/playwright/java:vv1.47.0-jammy
+      image: mcr.microsoft.com/playwright/java:v1.47.0-jammy
       options: --user 1001
     steps:
       - uses: actions/checkout@v4
@@ -165,7 +165,7 @@ trigger:
 
 pool:
   vmImage: ubuntu-latest
-container: mcr.microsoft.com/playwright/java:vv1.47.0-noble
+container: mcr.microsoft.com/playwright/java:v1.47.0-noble
 
 steps:
 - task: JavaToolInstaller@0
@@ -188,7 +188,7 @@ Running Playwright on CircleCI is very similar to running on GitHub Actions. In
 executors:
   pw-jammy-development:
     docker:
-      - image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
+      - image: mcr.microsoft.com/playwright/java:v1.47.0-noble
 ```
 
 Note: When using the docker agent definition, you are specifying the resource class of where playwright runs to the 'medium' tier [here](https://circleci.com/docs/configuration-reference?#docker-execution-environment). The default behavior of Playwright is to set the number of workers to the detected core count (2 in the case of the medium tier). Overriding the number of workers to greater than this number will cause unnecessary timeouts and failures.
@@ -199,7 +199,7 @@ Jenkins supports Docker agents for pipelines. Use the [Playwright Docker image](
 
 ```groovy
 pipeline {
-   agent { docker { image 'mcr.microsoft.com/playwright/java:vv1.47.0-noble' } }
+   agent { docker { image 'mcr.microsoft.com/playwright/java:v1.47.0-noble' } }
    stages {
       stage('e2e-tests') {
          steps {
@@ -216,7 +216,7 @@ pipeline {
 Bitbucket Pipelines can use public [Docker images as build environments](https://confluence.atlassian.com/bitbucket/use-docker-images-as-build-environments-792298897.html). To run Playwright tests on Bitbucket, use our public Docker image ([see Dockerfile](./docker.mdx)).
 
 ```yml
-image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
+image: mcr.microsoft.com/playwright/java:v1.47.0-noble
 ```
 
 ### GitLab CI
@@ -229,7 +229,7 @@ stages:
 
 tests:
   stage: test
-  image: mcr.microsoft.com/playwright/java:vv1.47.0-noble
+  image: mcr.microsoft.com/playwright/java:v1.47.0-noble
   script:
   ...
 ```

java/versioned_docs/version-stable/docker.mdx

@@ -22,7 +22,7 @@ This Docker image is intended to be used for testing and development purposes on
 ### Pull the image
 
 ```bash
-docker pull mcr.microsoft.com/playwright/java:vv1.47.0-noble
+docker pull mcr.microsoft.com/playwright/java:v1.47.0-noble
 ```
 
 ### Run the image
@@ -34,15 +34,15 @@ By default, the Docker image will use the `root` user to run the browsers. This
 On trusted websites, you can avoid creating a separate user and use root for it since you trust the code which will run on the browsers.
 
 ```bash
-docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:vv1.47.0-noble /bin/bash
+docker run -it --rm --ipc=host mcr.microsoft.com/playwright/java:v1.47.0-noble /bin/bash
 ```
 
 #### Crawling and scraping
 
 On untrusted websites, it's recommended to use a separate user for launching the browsers in combination with the seccomp profile. Inside the container or if you are using the Docker image as a base image you have to use `adduser` for it.
 
 ```bash
-docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:vv1.47.0-noble /bin/bash
+docker run -it --rm --ipc=host --user pwuser --security-opt seccomp=seccomp_profile.json mcr.microsoft.com/playwright/java:v1.47.0-noble /bin/bash
 ```
 
 [`seccomp_profile.json`](https://github.com/microsoft/playwright/blob/main/utils/docker/seccomp_profile.json) is needed to run Chromium with sandbox. This is a [default Docker seccomp profile](https://github.com/docker/engine/blob/d0d99b04cf6e00ed3fc27e81fc3d94e7eda70af3/profiles/seccomp/default.json) with extra user namespace cloning permissions:
@@ -75,10 +75,10 @@ See our [Continuous Integration guides](./ci.mdx) for sample configs.
 See [all available image tags].
 
 We currently publish images with the following tags:
-- `:vv1.47.0` - Playwright vv1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:vv1.47.0-noble` - Playwright vv1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
-- `:vv1.47.0-jammy` - Playwright vv1.47.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
-- `:vv1.47.0-focal` - Playwright vv1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
+- `:v1.47.0` - Playwright v1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:v1.47.0-noble` - Playwright v1.47.0 release docker image based on Ubuntu 24.04 LTS (Noble Numbat).
+- `:v1.47.0-jammy` - Playwright v1.47.0 release docker image based on Ubuntu 22.04 LTS (Jammy Jellyfish).
+- `:v1.47.0-focal` - Playwright v1.47.0 release docker image based on Ubuntu 20.04 LTS (Focal Fossa).
 
 :::note
 

java/versioned_docs/version-stable/intro.mdx

@@ -58,7 +58,7 @@ public class App {
     <dependency>
       <groupId>com.microsoft.playwright</groupId>
       <artifactId>playwright</artifactId>
-      <version>v1.47.0</version>
+      <version>1.47.0</version>
     </dependency>
   </dependencies>
   <build>

java/versioned_docs/version-stable/test-runners.mdx

@@ -198,7 +198,7 @@ repositories {
 }
 
 dependencies {
-  implementation 'com.microsoft.playwright:playwright:v1.47.0'
+  implementation 'com.microsoft.playwright:playwright:1.47.0'
 }
 
 application {
@@ -231,7 +231,7 @@ repositories {
 }
 
 dependencies {
-  implementation("com.microsoft.playwright:playwright:v1.47.0")
+  implementation("com.microsoft.playwright:playwright:1.47.0")
 }
 
 application {