Feature/api/marxan 196 migrate for bbox

[aagm]

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/G7eULYuARCxkP3efYurNH6LaQXnL
✅ Preview: https://marxan-git-feature-apimarxan-196-migrate-for-bbox-vizzuality1.vercel.app

marxan-storybook – ./app

🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/3qLahK1FPGqBmxCESfF3FUExnLbo
✅ Preview: https://marxan-storybo-git-feature-apimarxan-196-migrate-for-bbo-e82c1a.vercel.app

[kgajowy]

@Entity('admin_regions')
export class AdminArea ...

shouldn't it be updated as well?

[aagm]

That one is entending from the country View, so only defining it in the country should be more than enough

[kgajowy]

@aagm you don't have to expose it to frontend (i.e. don't put Api decorators) but I believe we should keep the code definitions really close (the same) as they are in the database - it will help with both generating migrations automatically AND keep the usage clean (right now, if you would like to use bbox from within the code - you can't; and in few months one will need to figure out that the column is there by reviewing every single migration where this table is present)