Update notebook for validation against multiple use cases

[JieXiong9119]

Any background context you want to provide?

The existing outputs from notebook examples could only be validated against one use case (the corresponding level of audit). There are several use cases that could be satisfied with simple modification to current examples.

What does this PR do?

1. So now the output example could be validated against these use cases: SEED, L200 Audit, L000 OS Pre-simulation, BRICR SEED

2. A few corrections on the example data

How should this be manually tested?

What are the relevant tickets?

https://github.com/BuildingSync/project-tracker/issues/119

Screenshots (if appropriate)

[JieXiong9119]

This PR is trying to enrich the example to cover as many use cases as possible, as to prove the generalisability among different use cases. This effort also shows mutual exclusivity between a few use cases.

The fundamental use case is L200 Audit. The other three use cases could be validated through adding a few elements:

• SEED
  • ScenarioName for all Scenarios
• BRICK SEED
  • ScenarioName for all Scenarios
• Required PremisesIdentifiers of "City Custom Building ID" and “Custom ID 1”
  • L000 OpenStudio Pre-Simulation
  • Modeled Scenario

Invalid use cases:

• L100 Audit (surprisingly 67 errors) & L100 OpenStudio Pre-Simulation (1 error)
  • Exclusive requirements of principalHVACSystem linked with spaces in L1000 and detailed HVACSystems linked with spaces in L200 (this is also the only conflict for L100 OpenStudio Pre-Simulation use case)
  • Specific requirements under ResourceUse for L100 Audit
• Bsyncr (1 error)
  • The strict requirement of single electricity ResourceUse by Bsyncr, conflicts with the subsystem-level electrical ResourceUse reported for L200 audit.
• Better (16 errors)
  • Specific requirements under ResourceUse
• City use cases: San Francisco (450 errors) & New York City (487 errors)
  • A lot of specific requirements from city use cases

I suggest we should make effort to address the compatibility between this example and L100 Audit use case in the future as they should be intuitively.