Consider making mod 3 workflow for TADA_MLSummaryRef to run after TADA_DefineCriteriaMethodology instead

[wokenny13]

Is your feature request related to a problem? Please describe:

Users who run one of the ExampleMod3AlternativeOptions.Rmd options to generate the TADA criteria table will need to define any unique spatial criteria to ML or AU if applicable generated from the function in TADA_MLSummary().

Users who proceed with one of the alternative options will not be able to run TADA_MLSummary() without running TADA_ParametersForAnalysis and TADA_UsesForAnalysis prior.

There should be a simpler way to define any unique spatial criteria for the case in which users proceed with the alternative options route. In addition, there will be one less function to run in the "auto_assign" method that will speed the function up - as it is not necessarily required to have the spatial ref defined during this step with generating the TADA criteria table from TADA_DefineCriteriaMethodology()

Describe the solution you'd like:

The current workflow is:
TADA_ParametersForAnalysis -> TADA_UsesForAnalysis -> TADA_MLSummaryRef -> TADA_DefineCriteriaMethodology()

suggested change in workflow:
TADA_ParametersForAnalysis -> TADA_UsesForAnalysis -> TADA_DefineCriteriaMethodology() -> TADA_MLSummaryRef