feat(geoprocessing): report progress of the marxan run

[Dyostiq]

Substitute this line for a meaningful title for your changes

Overview

Please write a description. If the PR is hard to understand, provide a quick explanation of the code.

Designs

Link to the related design prototypes (if applicable)

Testing instructions

Please explain how to test the PR: ID of a dataset, steps to reach the feature, etc.

Feature relevant tickets

Link to the related task manager tickets

---

Checklist before submitting

• Meaningful commits and code rebased on develop.
• If this PR adds feature that should be tested for regressions when
  deploying to staging/production, please add brief testing instructions
  to the deploy checklist (docs/deployment-checklist.md)
• Update CHANGELOG file

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

marxan – ./app

🔍 Inspect: https://vercel.com/vizzuality1/marxan/6rnJV6tVpXBcaYUP3TvcVCWFEhCd
✅ Preview: https://marxan-git-feature-marxan-477-report-progress-vizzuality1.vercel.app

marxan-storybook – ./app

🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/Ed1vGU31nG3GkEtE4jPhJXgfCGw2
✅ Preview: https://marxan-storybook-git-feature-marxan-477-repo-d15af7-vizzuality1.vercel.app

[kgajowy]

I believe it should rather base on pre-defined number of desired runs (derived form input.dat)

[hotzevzl]

for simplicity's sake we can even keep this as is - in practice (unless there's a bug in the Marxan CLI) the regex match should be equivalent to getting data from input.dat, but I like the idea of this being self-contained as is now.