Use $COMP_ROOT_DIR_LND in place of $SRCROOT for FATES testmods -- so can work in CESM or CAM checkouts

[ekluzek]

In several FATES testmods we use $SRCROOT to get the top level path of the CLM src directory. However, we should use COMP_ROOT_DIR_LND instead since $SRCROOT will be incorrect when working in a CESM or CAM checkout.

git grep SRCROOT shows the following files that should change...

cime_config/testdefs/testmods_dirs/clm/FatesColdPRT2/shell_commands:SRCDIR=`./xmlquery SRCROOT --value`
cime_config/testdefs/testmods_dirs/clm/FatesColdSeedDisp/README:file generated on the fly is placed in the $SRCROOT/src/fates/parameter_files
cime_config/testdefs/testmods_dirs/clm/FatesColdSeedDisp/README:directory.  This may still run into problems is the $SRCROOT string is too long.
cime_config/testdefs/testmods_dirs/clm/FatesColdSeedDisp/shell_commands:SRCDIR=`./xmlquery SRCROOT --value`
cime_config/testdefs/testmods_dirs/clm/FatesColdTwoStream/README:file generated on the fly is placed in the $SRCROOT/src/fates/parameter_files
cime_config/testdefs/testmods_dirs/clm/FatesColdTwoStream/README:directory.  This may still run into problems is the $SRCROOT string is too long.
cime_config/testdefs/testmods_dirs/clm/FatesSetupParamBuild/shell_commands:      SRCDIR=$(./xmlquery SRCROOT --value || echo "null")
cime_config/testdefs/testmods_dirs/clm/FatesSetupParamBuild/shell_commands:      check_error $? "Trouble getting SRCROOT from case"

[ekluzek]

I realized as a result of something that @rgknox asked about.

[johnpaulalex]

I believe #4024 already fixes this and is now in b4b-dev - @ekluzek do you concur?

[ekluzek]

I believe #4024 already fixes this and is now in b4b-dev - @ekluzek do you concur?

Yep, nice catch! Closing as fixed.