cleaner code: #17.1 decouple manual data from _setRotorParameters

[ombahiwal]

for the first point mentioned in Issue #17

• This PR doesn't exactly move the hardcoded values to bin
• but separates the manually entered data from _setRotorParameters into a _get_rotor_parameters(diameter) function to retrieve values, making it more cleaner.

The manual specification of rotor speed and blade pitch in the _setRotorParameters function can be replaced with a more dynamic and flexible approach. We can use external configuration files, a parameterized function, or a database. For now, I'll suggest a Python implementation where we dynamically load these parameters from a dictionary or a separate configuration file.

[rthedin]

We are going to hold off from merging this PR for now. Some offshore wind team members are currently looking into potential ways to incorporate this in a better way. Essentially the Hs and Tp values might be design variables, so we are considering adding that to the inputs and let the user have better control.