expand ax.scatter kwargs that can be used

[quaquel]

#2430 added the possibility to pass keyword arguments on to the various draw functions. This builds on that by passing any keyword arguments not used explicitly in any of the draw functions on to ax.scatter. This can, for example, be used to set a custom colormap, control vmin, vmax etc., as shown in the updated Boltzmann wealth example (see below for a screenshot)

Closes #1183.

[github-actions]

Performance benchmarks:

Model	Size	Init time [95% CI]	Run time [95% CI]
BoltzmannWealth	small	🔵 +1.8% [+1.0%, +2.5%]	🔵 -0.9% [-1.0%, -0.8%]
BoltzmannWealth	large	🔵 +1.2% [+0.7%, +1.7%]	🔵 -1.7% [-2.2%, -1.2%]
Schelling	small	🔴 +7.5% [+7.0%, +8.0%]	🔴 +12.8% [+12.4%, +13.2%]
Schelling	large	🔴 +8.7% [+7.2%, +10.2%]	🔴 +22.3% [+20.3%, +23.8%]
WolfSheep	small	🔴 +6.1% [+5.8%, +6.3%]	🔴 +4.1% [+4.0%, +4.3%]
WolfSheep	large	🔴 +9.1% [+7.6%, +10.5%]	🔴 +13.1% [+10.0%, +16.3%]
BoidFlockers	small	🔵 +2.9% [+2.4%, +3.4%]	🔵 +2.9% [+2.4%, +3.5%]
BoidFlockers	large	🔵 +1.3% [+0.5%, +2.1%]	🔴 +4.2% [+3.8%, +4.5%]

[EwoutH]

It’s so incredibly nice to see examples updated together with code. And thanks for the screenshot, always appreciated!

Looks clean, let’s give others also a bit of time to review.

At some point we should add a note or section about handeling axes and their arguments (including things like colormapping) to the tutorial. Can be a follow up.

[quaquel]

If linewith and edgecolor are handled analogously to color and size, basically everything in ax.scatter is controllable and we can also close #2341. I might just do that in a seperate PR to keep this one clear and focussed.

[EwoutH]

I would say go ahead and merge tomorrow morning, our US-timezone friends can check tonight and otherwise it's good to go.