docs(jdbc): add detailed explanation of JDBC driver types (Type-1 to Type-4)

What
- Documented all four JDBC driver types:
  1. **Type-1 (JDBC-ODBC Bridge)** → translates JDBC calls into ODBC.
  2. **Type-2 (Native-API Driver)** → uses database client libraries for native calls.
  3. **Type-3 (Network Protocol Driver)** → converts JDBC calls to DB-independent network protocol, translated by middleware.
  4. **Type-4 (Thin Driver)** → pure Java, translates JDBC calls directly into DB-native protocol.
- Included how each works, pros, cons, and dependencies.
- Highlighted portability issues, performance trade-offs, and compatibility.

Why
- Developers often struggle to choose the correct JDBC driver type.
- Clarifies the evolution of JDBC drivers from legacy (Type-1/2) to modern (Type-3/4).
- Helps in understanding why most modern systems use Type-4 drivers (thin, fast, fully Java).

How
- Broke down driver types into sections:
  - Working principle.
  - Advantages (speed, flexibility, portability).
  - Limitations (dependencies, performance overhead, DB-specific ties).
- Added context on Java’s deprecation of Type-1 and limited use of Type-2.
- Showed real-world relevance of Type-3 (middleware in enterprise apps) and Type-4 (direct DB connectivity).

Key Takeaways
- **Type-1 (ODBC Bridge)** → Legacy, slow, requires ODBC, deprecated.
- **Type-2 (Native API)** → Faster than Type-1 but requires DB-specific client libraries.
- **Type-3 (Network Protocol)** → Pure Java client + middleware, good for heterogeneous databases.
- **Type-4 (Thin Driver)** → Fastest, pure Java, directly speaks DB protocol (most widely used today).

Real-life Applications
- **Type-1**: Early Java applications bridging to legacy ODBC drivers.
- **Type-2**: Corporate systems tied to Oracle/SQL Server native client libraries.
- **Type-3**: Enterprise middleware solutions handling multiple DBs via a single protocol.
- **Type-4**: Modern Spring Boot / Hibernate apps connecting directly to MySQL, PostgreSQL, Oracle, etc.

Notes
- Type-3 and Type-4 are preferred for modern development due to platform independence.
- Type-4 is the industry standard in production apps because it balances speed, simplicity, and portability.
- Always choose the driver type based on application requirements, environment, and supported DBs.

Signed-off-by: https://github.com/Someshdiwan <[email protected]>

Author: Someshdiwan

Section28JDBCusingSQLite/JDBC/Database Programs.png renamed to Section28JDBCusingSQLite/JDBC/DatabasePrograms.png

@@ -1,4 +1,4 @@
-Explanation of JDBC Driver Types
+Explanation of JDBC Driver Types:
 
 1. Type-1 Driver (JDBC-ODBC Bridge)
    - How it works:
@@ -40,7 +40,7 @@ Explanation of JDBC Driver Types
      - Tied to a specific database’s protocol (e.g., MySQL, Oracle, etc.).  
      - If you need to support multiple databases, you need multiple Type-4 drivers (one for each database).
 
-Key Points to Remember
+Key Points to Remember:
 - Type-1 and Type-2 often require native code or ODBC, which adds dependencies and can affect portability.  
 - Type-3 and Type-4 are fully written in Java, making them more platform-independent and usually more
-  performant for modern applications.
+  performant for modern applications.