Rename JupyterViz to SolaraViz

[rht]

Fixes #2175.

[rht]

Note: JupyterViz is still available. It's an alias to SolaraViz. i.e. This is not a breaking change.

[github-actions]

Performance benchmarks:

Model	Size	Init time [95% CI]	Run time [95% CI]
Schelling	small	🔵 -1.2% [-1.5%, -0.9%]	🔵 +0.4% [+0.2%, +0.6%]
Schelling	large	🔵 -1.5% [-2.1%, -0.9%]	🔵 +1.2% [+0.4%, +1.8%]
WolfSheep	small	🔵 -0.8% [-1.9%, +0.4%]	🔵 -1.2% [-1.6%, -0.9%]
WolfSheep	large	🔵 -0.6% [-1.1%, -0.1%]	🔵 -1.6% [-3.5%, +0.5%]
BoidFlockers	small	🔵 +0.9% [+0.2%, +1.6%]	🔵 +1.3% [+0.7%, +1.9%]
BoidFlockers	large	🔵 +1.9% [+1.3%, +2.5%]	🔵 -0.6% [-1.1%, +0.1%]

[EwoutH]

Thanks for the PR! Just to double check, SolaraViz is the most descriptive and fitting name we could give the current visualisation, right? You said something about other backends, but that would be new classes right?

[rht]

Just to double check, SolaraViz is the most descriptive and fitting name we could give the current visualisation, right?

Actually, it could have been called just Visualization. But I'm fine either way.

Another backend would be Dash, see. e.g. vizro which has really good looking visualization: https://github.com/mckinsey/vizro.

[EwoutH]

But then that would be a new function right? So instead of importing

from mesa.visualization import SolaraViz

We add a new, second function called DashViz for visualization, so you could also do:

from mesa.visualization import DashViz

[rht]

Yes, it would be a new function/class.