--adjust_data crashes if features were removed during munging in earlier stages

[m-makarious]

Please make sure that this is a bug.

System information:

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Catalina
• GenoML Installed from (source or binary): Source
• GenoML Version: v1b6
• Python Version: 3.7+

Describe the current behavior: Currently, munging removes features prior to Z-scoring if they have a standard deviation of 0 or remove SNPs if the --gwas and --p flags are indicated as well, so when it is time to adjust the data by the target features indicated by the user in the .txt file, some of those features were dropped earlier - causing GenoML to crash

Describe the expected behavior: Shouldn't crash - should keep going. Easy fix, compare the incoming .txt to the munged dataframe and adjust only by the features still remaining.

Code to reproduce the issue: Provide a reproducible test case that is the bare minimum necessary to generate the problem. Might not happen to everyone, especially if the dataset is small enough or only significant features are kept. See above for how we came across this

Other Information / Logs Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

[m-makarious]

When adjusting the data now, there's a check at the top looking at intersecting features between the incoming target list and the munged dataset, ensuring only features that are left are the ones getting adjusted for.

Code below: