Fix and test loading ORSO files

[jmborr]

What was broken:

• loading files using function load4. The import statement in webview's API was incorrect.

What is fixed:

• Fix import statment of function load4 in webview's API
• Unit test for funciton parse_orso()
• add orsopy as a dependency

Check all that apply:

• updated documentation
• Source added/refactored
• Added unit tests
• Added integration tests

Check list for the reviewer

• best software practices
  • clearly named variables (better to be verbose in variable names)
  • code comments explaining the intent of code blocks
• All the tests are passing
• The documentation is up to da

[bmaranville]

Can you describe what is broken, and then fixed by this PR?

[jmborr]

Can you describe what is broken, and then fixed by this PR?

Will this work?

What was broken:

• loading files using function load4. The import statement in webview's API was incorrect.

What is fixed:

• Fix import statment of function load4 in webview's API
• Unit test for funciton parse_orso()
• add orsopy as a dependency

[glass-ships]

@bmaranville do we have a preferred docstring style for this project?
I've noticed a couple different styles but it's hard to tell what the most common one used is,
especially given a lot of the latex expressions.

I lean toward google/numpy style, but if what jose has added in this PR is ok with you, I'm good with it.

[jmborr]

I lean toward google/numpy style, but if what jose has added in this PR is ok with you, I'm good with it.

I always favor Numpy style docstrings. They occupy a bit more lines but perhaps that's the reason I find them easier to read 😃

[jmborr]

@bmaranville @glass-ships thanks for reviewing this