chore: bump github.com/umee-network/umee/price-feeder from 0.2.1 to 0.2.4 (backport #322)

[mergify]

This is an automatic backport of pull request #322 done by Mergify.
Cherry-pick of d9fa470 has failed:

On branch mergify/bp/release/v0.3.x/pr-322
Your branch is up to date with 'origin/release/v0.3.x'.

You are currently cherry-picking commit d9fa470.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   cmd/peggo/orchestrator.go
	modified:   mocks/gravity_queryclient.go
	modified:   orchestrator/main_loops.go
	new file:   orchestrator/oracle/currency.go
	modified:   orchestrator/relayer/batch_relaying.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	both modified:   orchestrator/oracle/oracle.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[RafilxTenfen]

I think we are going to use 0.4.x from now on, So doesn't make sense to spend time backporting to 0.3.x
Closing this for now @facundomedica ^^