Avoid per-epoch limit for refunding

[yito88]

Describe your changes

Closes #4938.

Based on #4939

Checklist before merging

• If this PR has some consensus breaking changes, I added the corresponding breaking:: labels
  • This will require 2 reviewers to approve the changes
• If this PR requires changes to the docs or specs, a corresponding PR is opened in the namada-docs repo
  • Relevant PR if applies:
• If this PR affects services such as namada-indexer or namada-masp-indexer, a corresponding PR is opened in that repo
  • Relevant PR if applies:

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 0d34825.

✅ Passed Jobs With Interesting Signals

Pipeline	Job	Signal	Health on main	Retries	🔍 CI Insights	📄 Logs
Lint 🧹 Build 🛠️ Test 🚦	test-e2e (2)	Base branch is broken, but the job passed. Looks like this might be a real fix 💪		0	View	View
	test-integration	Base branch is broken, but the job passed. Looks like this might be a real fix 💪		0	View	View

[brentstone]

@yito88 want to make sure - this closes #4938 right?

[yito88]

Yes, this closes #4938. Thanks for the update

[sug0]

these two unit tests are now failing:

    vp::tests::test_timeout_on_close_packet
    vp::tests::test_timeout_packet

[sug0]

lgtm. please add a changelog

[brentstone]

Is this rdy for merge? @yito88 @tzemanovic @sug0

[sug0]

@brentstone it's ready, but I was waiting on #4939 to be approved+merged, since this PR is pretty simple, but it would introduce conflicts on #4939