harmonize terminology across codebase

[handwerkerd]

Summary

Particularly with the addition of the modularization decision tree #756, there are places where similar things are given different names in various parts of the codebase. This might create some unnecessary confusion and risks for typos

Additional Detail

Places for harmonizing terminology includes:

• using component_table rather than comptable everywhere
    - Decide whether to standardize on d_table_score vs mean_metric_score
• Have the PCA component table better match the ICA component table (primarily changing from rationale to classification_tags terminology. (This is currently only an issue for the kundu selection process for PCA components.)

Places to reduce typo risks:

• Make all classification and classification_tag labels either fully case insensitive or changed to match the capitalization of where classification and tag labels are defined.
• Create a field in the tree json for classification_tag_explanations In it would be a dictionary for each tag in the tree and an explanation for what that tag means. Then explanations for the tags in any given tree would automatically be included in the report rather than having us need to maintain a hard coded list of explanations in the documentation.

Next Steps

• Wait for [REF] Decision Tree Modularization #756 to merge
• Since this will require a lot of small changes across the code base, find a time when no one else is making dramatic code edits so that this can happen quickly.