chore: remove ipython from development dependencies

[mistercrunch]

Summary

removing ipython as it's simply a nice-to-have, but not required for Superset development

[john-bodley]

I thought development dependencies were there to help aid development. Maybe it's worth explicitly mentioning in the documentation what are viable development dependencies.

[mistercrunch]

Yes for this particular one the "likely hood to be used" vs "dependency burden" ratio isn't great. Currently the criteria is more or less "commonly used by humans and/or CI for development workflows".

Now that we have a workflow to upgrade things (supersetbot as a pip-compile-multi-aware dependabot replacement), it seems reasonable / manageable if we wanted to bring back more segmentation/complexity under requirements/ if we wanted to.

[mistercrunch]

One more thought it with segmentation in requirements/ we can have different level of rigor for freshness for different files. Likely I'll set up supersetbot in different ways for base.in VS development.in