feat: Move resource to another org from Resource Info Box

[Pallavikumarimdb]

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

• Enables resource move to a different org (via POST /resource/:resourceId/move-org)
• Displays other available orgs in ResourceInfoBox
• Core logic functional

✅ TODO in follow-up commits:

• More Enhancement
• Add tests and error edge cases
• Add i18n translation strings

Fix: #1108

How to test?

[oschwartz10612]

Looking good so far thanks for this pr!

One thing to note: we are actively working on an update that moves the siteId from the resource to the target. So there is a siteId on the target in the database and NOT on the resource. When you move a resource to a new org we might need to kick these sites off of the targets and show that somehow in the UI. We plan to have some of this merged from the target-sites branch soon.

Also one other thing I think you are thinking about a bit but is worth mentioning: when you move it the users and the roles and stuff assigned to that resource no longer apply because they are from the old org. So that all needs to be cleaned up in the database and I guess the new org will just have the current user with access. You can obviously keep the pin and pass and stuff.

Let us know if you have any questions!

[Pallavikumarimdb]

Looking good so far thanks for this pr!

One thing to note: we are actively working on an update that moves the siteId from the resource to the target. So there is a siteId on the target in the database and NOT on the resource. When you move a resource to a new org we might need to kick these sites off of the targets and show that somehow in the UI. We plan to have some of this merged from the target-sites branch soon.

Also one other thing I think you are thinking about a bit but is worth mentioning: when you move it the users and the roles and stuff assigned to that resource no longer apply because they are from the old org. So that all needs to be cleaned up in the database and I guess the new org will just have the current user with access. You can obviously keep the pin and pass and stuff.

Let us know if you have any questions!

Thanks for the feedback!

I'll go ahead and implement the Permission & Access Management part — (Cleaning up the old org’s user/role associations from the resource and assigning the current user under the new org). I'll make sure the pin and pass remain intact.

For the Site-Target Relationship Handling, I'll hold off until the updates from the target-sites branch are merged.