Fix bounds after reversing coordinate values

[sloosvel]

Description

This pull request flips back the coordinate bounds if they have been reversed when checking the coordinate direction

• Closes Reversing coordinates using iris.util.reverse flips the bounds incorrectly #1060
• Link to documentation:

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

• PR has a descriptive title for the changelog
• Labels are assigned so they can be used in the changelog
• Code follows the style guide
• Documentation is available for new functionality
• YAML files pass pre-commit or yamllint checks
• Circle/CI tests pass
• Codacy code quality checks pass
• Documentation builds successfully on readthedocs
• Unit tests are available

If you make backwards incompatible changes to the recipe format:

• Update ESMValTool and link the pull request(s) in the description

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[sloosvel]

Actually I am not sure if this is right, or if it's a weird issue with a specific dataset. I'll check and close it if that is the case.

[sloosvel]

So it is indeed a bug, but the implementation in the first commit was not quite right. This should do it.

[valeriupredoi]

nice one, cheers @sloosvel

[valeriupredoi]

So it is indeed a bug, but the implementation in the first commit was not quite right. This should do it.

If this is a bug generalized to all datasets, then it's good to go 👍

[sloosvel]

@jvegasbsc we need this for some obs data! And @valeriupredoi thinks it's good to go.