Remove some comments in the LII2FINIDATAREAS test

I don't *think* it is the case any more that having
GLC_TWO_WAY_COUPLING=TRUE makes this test more powerful. (I'm thinking
that this stopped being true once we resolved
ESCOMP#340, which was also when the
standard LII test stopped needing GLC_TWO_WAY_COUPLING=FALSE. But I may
be forgetting some reason why GLC_TWO_WAY_COUPLING is still preferable
in this LII2FINIDATAREAS test.)

cime_config/SystemTests/lii2finidatareas.py

@@ -1,17 +1,11 @@
-"""
-Implementation of the LII2FINIDATAREAS test.
+"""Implementation of the LII2FINIDATAREAS test.
 
 This is similar to the LII test, but tests init_interp with mode
 'use_finidat_areas'.
 
-As with the standard LII test, this must be used in a configuration for
-which we have a compatible out-of-the-box finidat file (so that the run
-with use_init_interp = .false. runs successfully). In constrast to our
-standard LII test (which uses glcMEC_spunup_1way), this one can use a
-standard CISM2%NOEVOLVE configuration: we do *not* need to set
-GLC_TWO_WAY_COUPLING=FALSE; in fact, it's a better test if we have
-GLC_TWO_WAY_COUPLING=TRUE: with this mode of operation, areas should
-match between the two runs.
+As with the standard LII test, this must be used in a configuration for which we have a
+compatible out-of-the-box finidat file (so that the run with use_init_interp =
+.false. runs successfully).
 
 It may not be totally necessary to have a system test covering this
 init_interp_method: between unit tests and inline checks, we have quite