Add organization status and rejection reason fields

[FangHsin0122]

Description

Backend support for the organization lifecycle in #1204.
The frontend is built (demo Video): An admin moves an organization through Pending → Active / Rejected with a reason captured on rejection, and Active ↔ Suspended.

The record currently only has active (boolean), which can't express these states.

Fields needed on stakeholder (type = organization)

Column	Type	Notes
status	enum / varchar	pending / active / suspended / rejected
rejection_reason	text	set when status = rejected

Endpoints

No new endpoint. The frontend already uses these (on stakeholder-api).
They only need to carry the two fields:

Method	Endpoint	Change
GET	/stakeholders/{id}	return status and rejection_reason
PATCH	/stakeholders/{id}	accept status and rejection_reason

Placement
I opened this in admin-api per Seba, though the frontend currently connects to stakeholder-api (/stakeholders).

A couple of quick questions to @dadiorchen

1. Which repo should own these fields? Admin-api or stakeholder-api?
2. Should status live in the stakeholder schema, or a separate SaaS schema?

Happy to move the issue wherever it fits best.

[cynthiabondi]

@FangHsin0122 , thanks for this, can you please add this ticket to the admin client repo instead of this one so they can be linked together?

[FangHsin0122]

Hi @cynthiabondi , I'd love to move it but I don’t have the permissions to transfer this to the admin client repo I think. The 'Transfer issue' button isn’t available to me. Please let me know if there’s anything I can do on my end.

[cynthiabondi]

No problem I will find way to move it and also follow up with Dadior on your questions. Thanks for the demo! @FangHsin0122