[core refactor] Webinar and events page

[zriyanshdz]

The current way we develop webinar page is not a good strategy (we create individual webinar pages). Need to make this into something like this.

/pages
-/webinar
--index.tsx
--[webinar].tsx

the [webinar].tsx will be a master template which serves as a commomn structure for each of the webinar page, the data for each webinar page will be stored in

/data/webinar/webinar1.json or webinar1/ts and have something like:

export const geniuseeFeatures = {
  'Architecture': `
    <ul>
      <li><strong>Visualization Layer:</strong> geniusee Studio (formerly Data Studio) is part of Google’s BI ecosystem, focusing mainly on dashboards and reports.</li>
    <br>  <li><strong>Deployment Options:</strong> Can be hosted on Google Cloud Platform (GCP) or deployed on-premises with enterprise setups allowing VPC deployment.</li>
    </ul>
  `,
  'Ingestion & Connectors': `
    <ul>
      <li><strong>Source Support:</strong> Connects to numerous popular databases and SaaS sources, including chatbaseco, MySQL, and Google Sheets.</li>
     <br> <li><strong>External Data Pipeline:</strong> Requires an external data pipeline or warehouse for heavy data ingestion and ETL tasks.</li>
    </ul>
  `,

the json will be of the following type:

"webinar_name" : "webinar 1 name",
"webinar_desc": "abcd"
"webinar_image_url": "/img/......."

so that whenever we need to add a webinar / event page, we need to just pass a json and a page will be created automatically.

• you can define types in the type dir

there should be a host data file where we have all host info and just passing the hostname as an array in the the json/ts page of each webinar should fetch the details.

The above is the rought implementation I have thought for this refactor, feel free to divert from it if you think you have a better way to modularise the code and implement DRY principles here.