Support negative offset for Background2d.to_3d

[AtreyeeS]

This fixes #4950

I don't think having the first bin centered on zero is necessarily prevented by the GADF, so I just adapted the to_3d function

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4e49533) 75.71% compared to head (4059606) 75.71%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4978   +/-   ##
=======================================
  Coverage   75.71%   75.71%           
=======================================
  Files         228      228           
  Lines       33775    33778    +3     
=======================================
+ Hits        25573    25576    +3     
  Misses       8202     8202           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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 921f1a9d3b5400e02968b78cf264ad9154840c10

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

git commit -am 'Backport PR #4978: Support negative offset for Background2d.to_3d'

4. Push to a named branch:

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

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

"Backport PR #4978 on branch v1.0.x (Support negative offset for Background2d.to_3d)"

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.

[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.1.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 921f1a9d3b5400e02968b78cf264ad9154840c10

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

git commit -am 'Backport PR #4978: Support negative offset for Background2d.to_3d'

4. Push to a named branch:

git push YOURFORK v1.1.x:auto-backport-of-pr-4978-on-v1.1.x

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

"Backport PR #4978 on branch v1.1.x (Support negative offset for Background2d.to_3d)"

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.