Update deploy script and add 1.4.3 updates (apache#9519)

site/README.md

@@ -119,6 +119,10 @@ make build OFFLINE=true
 ## Release process
 
 Deploying the docs is a two step process:
+
+> [!WARNING]  
+> The `make release` directive is currently unavailable as we wanted to discuss the best way forward on how or if we should automate the release. It involves taking an existing snapshot of the versioned documentation, and potentially automerging the [`docs` branch](https://github.com/apache/iceberg/tree/docs) and the [`javadoc` branch](https://github.com/apache/iceberg/tree/javadoc) which are independent from the `main` branch. Once this is complete, we can create a pull request with an offline build of the documentation to verify everything renders correctly, and then have the release manager merge that PR to finalize the docs release. So the real process would be manually invoking a docs release action, then merging a pull request.
+
  1. Release a new version by copying the current `/docs` directory to a new version directory in the `docs` branch and a new javadoc build in the `javadoc` branch.
     ```
     make release ICEBERG_VERSION=${ICEBERG_VERSION}

site/dev/deploy.sh

@@ -20,5 +20,5 @@ set -e
 
 ./dev/setup_env.sh
 
-mkdocs gh-deploy --dirty # --remote-branch asf-site
+mkdocs gh-deploy --remote-name "${REMOTE}"  # --remote-branch asf-site
 

site/mkdocs.yml

@@ -78,7 +78,7 @@ markdown_extensions:
       permalink: 🔗
 
 extra:
-  icebergVersion: '1.4.2'
+  icebergVersion: '1.4.3'
   social:
     - icon: fontawesome/regular/comments
       link: 'https://iceberg.apache.org/community/'

site/nav.yml

@@ -22,6 +22,7 @@ nav:
     - Hive: hive-quickstart.md
   - Docs: 
     - latest: '!include docs/docs/latest/mkdocs.yml'
+    - 1.4.3: '!include docs/docs/1.4.3/mkdocs.yml'
     - 1.4.2: '!include docs/docs/1.4.2/mkdocs.yml'
     - 1.4.1: '!include docs/docs/1.4.1/mkdocs.yml'
     - 1.4.0: '!include docs/docs/1.4.0/mkdocs.yml'