Fixed rewards settings bundle creation on Android

[SergeyZhukovsky]

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
  • Windows
  • macOS
  • Linux
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

Closes brave/brave-browser#1801

[NejcZdovc]

@SergeyZhukovsky can you please create issue for it an add auto closing tag into the commit

[NejcZdovc]

master e5e45dc
0.57.x 13d24ae
0.56.x b646472
0.55.x a368445

[bbondy]

Changing merged label to 0.56.x since this won't be included with 0.55.x hotfix2.