ISL Verse Marker dont rely on bible data that is uploaded to identify verse validity

[RevantCI]

ISL Verse Marker dont rely on bible data that is uploaded to identify verse validity during operations like POST and PUT
API - /isl-verse-markers
You can use this versification json, it can be added to the code base.
It can be made into a csv and inserted into the database on startup.
CREATE TABLE versification_schemas (
id SERIAL PRIMARY KEY,
name VARCHAR(100) NOT NULL UNIQUE, -- e.g. 'eng', 'org', 'kjv'
description TEXT,
data JSONB NOT NULL, -- the full JSON blob
is_default BOOLEAN DEFAULT FALSE,
created_at TIMESTAMPTZ DEFAULT NOW(),
updated_at TIMESTAMPTZ DEFAULT NOW()
);

-- Ensure only one default
CREATE UNIQUE INDEX idx_versification_default
ON versification_schemas(is_default)
WHERE is_default = TRUE;
https://github.com/Bridgeconn/isl-manzil-web/blob/main/web-app/src/assets/data/versification.json

• Add versification db model and corresponding pre population of data with app statrtup - 1 hr
• Changing the helper function in crud - 0.5 hr
• testing - 0.5 hr
• testing @NoelSudhish - 2.5hr
• Review and merge -1 hr -Athulya

[NoelSudhish]

currently isl verse markers api checks verse validation direct using versification json and not using TABLE versification_schemas

[JesniJ]

Test Result

Verified that the ISL Verse Markers API no longer relies on uploaded Bible data for verse validation during POST and PUT operations.

As confirmed by the dev team, the API is currently validating verses directly using the versification JSON instead of the versification_schemas table. Verse validation is functioning correctly based on the provided versification data, and CRUD operations are working as expected. No issues were observed during testing.

Moving the issue to done.

[tejaswini143]

.