Solve ASM2D Flowsheet without bound_push and autoscale function

[adam-a-a]

Fixes/Resolves:

Summary/Motivation:

An existing flowsheet example for the conventional ASM2D model uses bound_push and an autoscale function. Neither should be used to solve the model in the main codebase. Moreover, the modified version of ASM2D, a trickier variant of conventional ASM2D, will subsequently be implemented in a similar flowsheet example, but we should make sure the original version works first.

TODO:

• Adjust regression test values and review to make sure we accept the variations in results

Changes proposed in this PR:

• remove bound_push
• remove autoscaling

Legal Acknowledgement

By contributing to this software project, I agree to the following terms and conditions for my contribution:

1. I agree my contributions are submitted under the license terms described in the LICENSE.txt file at the top level of this directory.
2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

[adam-a-a]

Note: initialization and solve was working last I checked. All I need to do is update regression test values accordingly since they were apparently sensitive to the change in scaling.

[bknueven]

I think my meta-comment is this could be okay -- though it would be better to run calculate_scaling_factors after the unit model is initialized instead. Sometimes it is difficult to know good scaling factors without a solution in hand.

If things still "work" at the flowsheet level having a few custom options which just need to be utilized for unit model initialization isn't a huge deal, IMHO, even if it's less than ideal.