Seperate out entering health facility id and bridge registration

[khavinshankar]

Currently, when the ABDM health facility ID is linked (created or updated) via care UI, in the backend it is registered as a service in the ABDM bridge, and if the registration is successful the health ID is created or updated in care.

Separate out both processes, i.e., Data entry and registering the service with the bridge, so that the ops team can link the facilities before getting the production keys.

And registering with the bridge can happen after getting the keys.

We can add a boolean field to track if the id is registered as a service in the bridge, and we can register it before using it in an API call if the flag is false.

[github-actions]

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

[khavinshankar]

done