After 3.39 release, void unvoided form mappings

Product Bug: https://app.zenhub.com/workspaces/avni-product-635b73bded85e50018871ae6/issues/gh/avniproject/avni-server/544

Workaround done: unvoided voided form mappings - executed below code:

```
update form_mapping
set is_voided = false ,
last_modified_by_id = 6365,
last_modified_date_time = now()
where id in (24814,
24815);

update form_mapping
set is_voided = false ,
last_modified_by_id = 6365,
last_modified_date_time = now()
where id in (24528,
24529);

update form_mapping
set is_voided = false ,
last_modified_by_id = 6365,
last_modified_date_time = now()
where id in (23735,
23736);

update form_mapping
set is_voided = false ,
last_modified_by_id = 6365,
last_modified_date_time = now()
where id in (26951,
26952
);

update form_mapping
set is_voided = false ,
last_modified_by_id = 6365,
last_modified_date_time = now()
where id in (
26949,
26950
);

```
so now need to void below form mappings with ids: 24814, 24815, 24528, 24529, 23735, 23736, 26951, 26952, 26949, 26950

For data consistency reason and to avoid any confusion, need to void it again.

Start by reviewing the SQL statements in the issue and the form_mapping records for the listed IDs. Confirm the intended data state, apply the voiding change through the project's normal database process, and verify that all ten mappings have is_voided set consistently.

Written by the indexing model from the issue text.