Add CRUD API calls for ISL Verse markers

[RevantCI]

Add CRUD API calls for ISL Verse markers
use same table struture as ISL Admin to avoid reengineering the API calls

1. IslVerseMarkers(Base):
   id = Column(Integer, primary_key=True, index=True)
   isl_video_id = Column(Integer, ForeignKey("isl_bible.id", ondelete="CASCADE"),
   nullable=False, unique=True)
   verse_markers_json = Column(JSONB, nullable=False)

2. Check valid verse for book and chapter and allow merged verse eg 12_13
   Allow chapter and verse 0 for intro if verse markers added later
   see this file for time stamp format - https://github.com/Bridgeconn/isl-manzil-web/blob/main/web-app/src/assets/data/verse_markers/1%20Corinthians_5.csv

3. Ensure time stamp are in correct order increasing with each verse

4. Make Crud Calls as in ISL admin except POST call
   POST call
   {
   1: [ // isl_video_id ref isl_table id col
   { //verse_markers_json
   "verse": 0,
   "time": "00:00:00:00"
   }
   ]
   }

QA

• Testcases (ATT : 30 mins)
• Testing(ATT : 1 hr)
• Testing Review(ATT : 15 mins)

[JesniJ]

Test Result

Verified the CRUD API calls for ISL Verse Markers. The APIs are functioning correctly using the same table structure as the existing ISL Admin implementation.

Validation checks are working as expected:

• Valid book/chapter/verse combinations are accepted.
• Merged verses (e.g., 12_13) are supported correctly.
• Chapter 0 and verse 0 are accepted for intro markers.
• Timestamp format validation is working correctly, and timestamps are enforced in increasing order.

The POST request structure is functioning as expected, and CRUD operations are successfully creating, updating, retrieving, and deleting verse marker data without issues.

Moving the issue to done.