Our organization is split into development teams, which "owns" their project groups.

The developers can release all they want up to our staging environment, however to promote the release from Staging to Production we have a manual intervention step, that needs to be approved before a release can be promoted.

This works fine, and the team responsible can approve the manual intervention step and promote the release.
However.. this is kinda bad practice that in theory a given developer can code, build and release their changes all the way up to Production.

Can you add a feature so the approver can't be the same user which created the release? This would fit nicely as a peer review.

A specific approver team would not fit the bill here, as the developers might in turn approve eachothers release and sign off on the QA.