refactor: institutions table schema refactor and acadamic stream route

title: "refactor(backend): institutions table schema refactor and acadamic stream route"

♻️ Refactoring Request

Describe the current situation

Refactor the institution table schema for more normalized schema and crate a new get /institutions/academic-stream endpoint and refactor the get /institutions/universities?academic-stream and get /institutions/colleges?university and other filters

also add a new geo coord field in the institutions and write the necessary endpoints and services for it.

Describe the suggested refactoring

Right now the institutions table schema is not normalized and if a institution has multiple course_names then we will have n no of records for the same institution with multiple courses

Benefits of the refactoring

Explain the advantages of implementing this refactoring.

Potential impact or risks

Are there any potential risks or breaking changes associated with this refactoring?

Additional context

Add any other context, code snippets, or diagrams here.

📌 Follow semantic issue titling convention: <type>(<scope>): <description> (e.g., refactor(auth): simplify token validation logic or perf(database): optimize query performance).