Deprecation warnings for all variables since v.1.0

[xjjiang]

Summary

This PR targeted Issue #1289. I am sure this is not the final version but maybe a good point to start.

Related Issues

• Resolves Add deprecation warnings for all variable hierarchy name changes since 1.0. #1289

Backwards incompatibilities

None

AI Usage

None

[jkirk5]

I had some ideas on how to use the check on the original issue (#1289) - it is kind of similar to your idea but a little different

[Kenneth-T-Moore]

I am glad that you did this!

Might be easier if you just stored the deprecated var information in a dictionary keyed by the strings in the first column (old varnames).

{ "aircraft:design:thrust_takeoff_per_eng" : (removed, '#1142','1.0.0'), ...

Then you don't have to read a file, and the logic for checking it becomes

if var_name in deprecated_vars:
    raise error and give new name and info
else:
    raise warning that the name wasn't found.

[Kenneth-T-Moore]

Here is a little migration guide I made that might help catch some more variables. I closed my PR since it is stale, and your solution is a better approach.

#1125