Tool: update AMReX dependency (#1710)

* Tool: update AMReX dependency

We currently pull the `development` branch of AMReX in CMake builds.

This is problematic in central workflows:
- checking out a release might not compile
- manual intervention is needed by users
- builds are not as reproducibile as they could be
- CI fails in a surprising wary in WarpX if a temporary bug is lands
  in AMReX' `development`

Instead, we can bump the AMReX requirement periodically in a PR.
This migh be the case when we:
- need new features or bug fixes
- do a release

Manual updates guarantee that we see problems with updates from
AMReX in the moment they are introduced - during a PR that changes
the dependency to AMReX.

* Tool: update PICSAR dependency

See AMReX' updater description.

* Docs: Dependencies & Releases

Update and add workflows.

* PICSAR & AMReX: Bump Version to HEAD

Bump the PICSAR and AMReX versions to the latest head.
Executed with:
```
./Tools/Release/updateAMReX.py
./Tools/Release/updatePICSAR.py
```

* Python Tools: Cleanup

* Fix typos

Co-authored-by: Luca Fedeli <luca.fedeli@for.unipi.it>

Co-authored-by: Luca Fedeli <luca.fedeli@for.unipi.it>

1 files changed, 0 insertions, 65 deletions

diff --git a/Tools/DevUtils/update_release.sh b/Tools/DevUtils/update_release.sh
deleted file mode 100755
index 74e88cbf8..000000000
--- a/Tools/DevUtils/update_release.sh
+++ /dev/null
@@ -1,65 +0,0 @@
-#!/usr/bin/env bash
-
-# Copyright 2020 Maxence Thevenet
-#
-# This file is part of WarpX.
-#
-# License: BSD-3-Clause-LBNL
-
-
-# This script updates release version number in all source files.
-#
-# updates occurences like "version = '??.??'" where ??.?? is the version number
-# updates occurences like "WarpX v??.??" where ??.?? is the version number
-#
-# Requirements:
-# - gnu grep (default grep on MacOS does not have same -P option)
-# - gnu sed  (default grep on MacOS does not have same -i option)
-
-set -e
-
-# Get old tag number from git
-git_tag=`git describe --tags`
-old_release_number="${git_tag%%-*}"
-
-# Construct new tag number from current date
-d=`date +%Y.%m`
-new_release_number=${d:2}
-
-echo "Replace release number $old_release_number by $new_release_number"
-
-# Loop over files and sed patterns with version number
-pattern="\.c$|\.cpp$|\.F90$|\.h$|\.H$|\.ini$|\.md$|\.py$|"\
-"\.rst$|\.sh$|\.tex$|\.txt$|\.xml$|\.yml$|"\
-"CMakeLists\.txt|inputs"
-for i in $(find ../.. \
-                -not -path "../../.git/*"   \
-                -not -path "../../.idea/*"  \
-                -not -path "../../Docs/source/api/*" \
-                -not -path "../../Docs/build/*" \
-                -not -path "../../Docs/doxyxml/*" \
-                -not -path "*wp_parse*" \
-                -not -path "../../tmp_build_dir/*" \
-                -type f | \
-           grep -P "${pattern}")
-do
-    echo $i
-    # update occurences like "version = '??.??'" where ??.?? is the version number
-    # Note: sleep is required due to a bug in sed: without, the file
-    # permissions are modified
-    sed -i "s/version = "\'"$old_release_number"\'"/version = "\'"$new_release_number"\'"/g" $i && sleep .001
-    # update occurences like "WarpX v??.??" where ??.?? is the version number
-    sed -i "s/WarpX v$old_release_number/WarpX v$new_release_number/g" $i && sleep .001
-done
-
-echo ""
-echo "WARNING: Remaining occurences of $old_release_number are listed below."
-echo "         Is this expected? Or should these be updated too?"
-echo ""
-git grep "$old_release_number" . || echo ""
-echo "In order to get a list of PRs merged since date <date>, you can run:"
-echo "git log --since=<date> | grep -A 3 \"Author: \" | grep -B 1 \"\-\-\" | sed '/--/d' | sed -e 's/^    /- /'"
-echo "where <date> is replaced by the date since last relate, say 2020-02-02"
-# The actual command is below (commented), the one in echo above
-# has escape characters for printing purpose.
-# git log --since=<date> | grep -A 3 "Author: " | grep -B 1 "\-\-" | sed '/--/d' | sed -e 's/^    /- /'