Separate units in pcolormesh

[registerrier]

Description

This pull request solves #4754 by applying pcolormesh on the values rather than the quantity object.

Dear reviewer

[registerrier]

For compatibility this should be backported.

[codecov]

Codecov Report

Merging #4755 (e53e1ea) into main (1f1a57a) will increase coverage by 0.01%.
Report is 12 commits behind head on main.
The diff coverage is 88.57%.

@@            Coverage Diff             @@
##             main    #4755      +/-   ##
==========================================
+ Coverage   76.00%   76.02%   +0.01%     
==========================================
  Files         223      223              
  Lines       32019    32053      +34     
==========================================
+ Hits        24337    24367      +30     
- Misses       7682     7686       +4     

Files Changed	Coverage Δ
gammapy/estimators/map/core.py	92.80% <69.23%> (-0.63%)	⬇️
gammapy/estimators/map/tests/test_core.py	96.76% <100.00%> (+0.21%)	⬆️
gammapy/irf/background.py	93.56% <100.00%> (+0.07%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[registerrier]

During dev meeting, we agreed to keep a unit test to check for pcolormesh and Quantity. This will be in a future PR.

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v1.0.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 4009fc4d6c99dbb955bedda76f5e4ae874f3a088

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #4755: Separate units in pcolormesh'

4. Push to a named branch:

git push YOURFORK v1.0.x:auto-backport-of-pr-4755-on-v1.0.x

5. Create a PR against branch v1.0.x, I would have named this PR:

"Backport PR #4755 on branch v1.0.x (Separate units in pcolormesh)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.