Need to update our Fork and Tags for IDAES

[aladshaw3]

IDAES will be changing a lot of its paths for import statements for specific unit models and properties that we will be dependent on (see the comment and test failures in #502).

After updating the fork and tags for installing the latest IDAES, we will likely see a lot of depreciation warnings for those import statements. We will also need to then go through our code base and update those import paths.

• Update fork of IDAES and tag for installation
• Update all import paths in WaterTAP to IDAES models/properties

[aladshaw3]

I am not sure what the priority on this will be, but we should discuss this at the next meeting so we understand how much of a change this is and what this may 'break' in WaterTAP.

[bknueven]

Based on the issues in #500, we should ideally update to at least this commit: IDAES/idaes-pse@2cb6df0 (or just 2.0.0a1), and also update our Pyomo requirement to pyomo>=6.3 to get the latest version of PyNumero.

[adam-a-a]

Based on the issues in #500, we should ideally update to at least this commit: IDAES/idaes-pse@2cb6df0 (or just 2.0.0a1), and also update our Pyomo requirement to pyomo>=6.3 to get the latest version of PyNumero.

Yes, and I would consider this high priority since this is something that can hold up simple PRs.

[ksbeattie]

I will update the fork and put a tag on the 2cb6df0 hash, and open a PR to update our setup.py to use that.

[aladshaw3]

Closed by #512