fix(platform): ensure order for cached pr's on gitea and bitbucket

[viceice]

Changes

Reverse the cached pr list, so renovate finds the most recent PR first.

Context

Currently the cache returns pr's in accending order, so renovate always finds the oldest PR if multiple match.
So it opens new PR's event if a newer PR was already closed.
We do this sorting on github pr cache.

• closes fix(bitbucket): use last created PR in decision process #32672

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

I think it's very unlikely that a user closes a newer renovate PR and then re-opens an older PR.

[renovate-release]

🎉 This PR is included in version 39.88.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.88.1

Your semantic-release bot 📦🚀