Remove Anvil machine configs and support

docs/developers_guide/adding_new_machine.md

@@ -35,7 +35,7 @@ machines from hostnames with the following regular expressions:
 ```python
 '^chr-\d{4}'  # Chrysalis compute nodes with hostnames chr-0000 to chr-9999
 '^compy'      # Compy nodes with hostname compy
-'^n\d{4}'     # Anvil nodes with hostnames n0000 to n9999
+'^dane\d{1,4}' # Dane nodes with hostnames dane0 to dane9999
 ```
 
 In some cases, the hostname assigned to a machine is too generic to 
@@ -58,4 +58,3 @@ Identifying the machine by environment variables is **not recommended** unless
 absolutely necessary.
 :::
 
-

docs/users_guide/quick_start.md

@@ -31,7 +31,7 @@ function can also be used to detect which machine you are on.
 As an example, the result of `print(machine_info)` is:
 
 ```
-Machine: anvil
+Machine: chrysalis
   E3SM Supported Machine: True
   Compilers: intel, gnu
   MPI libraries: impi, openmpi, mvapich
@@ -72,9 +72,8 @@ you don't need to provide the machine name. It can be discovered automatically:
 
 - andes
 - aurora
-- anvil
-- chicoma-cpu
 - chrysalis
+- chicoma-cpu
 - compy
 - dane
 - frontier

docs/users_guide/sync/diags.md

@@ -14,7 +14,7 @@ The command supports two directions:
 
 Important constraints:
 
-- LCRC machines are `anvil` and `chrysalis`
+- LCRC machine is `chrysalis`
 - You may only:
   - run `to` when you are currently on an LCRC machine; and
   - run `from` when the other machine is an LCRC machine.
@@ -157,7 +157,7 @@ mache sync diags from <other> [-u <username>] [-m <this_machine>] [-f <config_fi
 
 Constraints enforced by the command:
 
-- Only `anvil`/`chrysalis` are considered LCRC machines
+- Only `chrysalis` is considered an LCRC machine
 - `to` is only allowed when you are on an LCRC machine
 - `from` is only allowed when the other machine is an LCRC machine
 - Do not attempt to sync between two different LCRC machines (there is no need