Replacing errors with warnings

[nikolayilyin]

Some of errors in the simulation output log are actually warnings because they are usually ignored. The goal of this issue is:

1. to figure out what errors among currently presented in the output files are actually warnings.
2. to replace those errors by warnings in the code.

In order to achieve the first goal one needs to analyze actual output logs, I think the good idea is to use existing simulation output from our spreadsheet , especially the runs with big numbers in the Error column.

For example: https://s3.us-east-2.amazonaws.com/beam-outputs/index.html#output/newyork/nyc-200k-baseline-04__2021-11-28_18-59-38_wvi https://s3.us-east-2.amazonaws.com/beam-outputs/index.html#output/newyork/nyc-200k-baseline-04__2021-11-28_17-32-45_ooc https://s3.us-east-2.amazonaws.com/beam-outputs/index.html#output/sfbay/smart-baseline-15k-FREIGHT__2021-11-29_14-33-42_lcm https://s3.us-east-2.amazonaws.com/beam-outputs/index.html#output/austin/austin-prod-200k-flowCap-0.2-speedScaling-1.1__2021-11-23_14-21-33_auf

or other recent runs