MINOR - 1.5.0 docs & update what's new (#17585)

* MINOR - Docs 1.5 upgrade

* quickstart

* docs

* what's new

openmetadata-docs/content/partials/v1.5/deployment/upgrade/upgrade-prerequisites.md

@@ -115,25 +115,73 @@ We believe this update will bring greater consistency and clarity to our version
 
 ## 1.5.0
 
-### Secrets Manager
+### Multi Owners
+OpenMetadata allows a single user or a team to be tagged as owners for any data assets. In Release 1.5.0, we allow users to tag multiple individual owners or a single team. This will allow organizations to add ownership to multiple individuals without necessarily needing to create a team around them like previously.
 
-- Starting with the release 1.5.0, the JWT Token for the bots will be sent to the Secrets Manager if you configured one. 
-  It won't appear anymore in your `dag_generated_configs` in Airflow.
+This is a backward incompatible change, if you are using APIs, please make sure the owner field is now changed to “owners”
 
-### Python SDK
-
-- `metadata insight` command removed.
-  Since Data Insights application was moved to be an internal system application instead of relying on external pipelines the SDK command to run the pipeline was removed.
+### Import/Export Format
+To support the multi-owner format, we have now changed how we export and import the CSV file in glossary, services, database, schema, table, etc. The new format will be
+user:userName;team:TeamName
+
+If you are importing an older file, please make sure to make this change.
+
+### Pydantic V2
+The core of OpenMetadata are the JSON Schemas that define the metadata standard. These schemas are automatically translated into Java, Typescript, and Python code with Pydantic classes.
+
+In this release, we have [migrated](https://docs.pydantic.dev/latest/migration/) the codebase from Pydantic V1 to Pydantic V2.
+
+### Deployment Related Changes (OSS only)
+
+`./bootstrap/bootstrap_storage.sh` **removed**
+
+OpenMetadata community has built rolling upgrades to database schema and the data to make upgrades easier. This tool is now called as ./bootstrap/openmetadata-ops.sh and has been part of our releases since 1.3. The `bootstrap_storage.sh` doesn’t support new native schemas in OpenMetadata. Hence, we have deleted this tool from this release.
+
+While upgrading, please refer to our Upgrade Notes in the documentation. Always follow the best practices provided there.
 
 ### Database Connection Pooling
 
-- OpenMetadata leverages Jdbi for database operations like reading, writing, and deleting. In this release, we've introduced new configuration options to enhance connection pooling, enabling more efficient database usage, especially in resource-constrained environments.
+OpenMetadata uses Jdbi to handle database-related operations such as read/write/delete. In this release, we introduced additional configs to help with connection pooling, allowing the efficient use of a database with low resources.
+
+Please update the defaults if your cluster is running at a large scale to scale up the connections efficiently.
+
+For the new configuration, please refer to the [doc](https://docs.open-metadata.org/latest/deployment/database-connection-pooling) here
 
-If your cluster operates at a large scale, consider updating these default settings to optimize connection management.
+### Data Insights
 
-For detailed information on the new configurations, please refer to the [documentation](/deployment/database-connection-pooling).
+The Data Insights application is meant to give you a quick glance at your data's state and allow you to take action based on the information you receive. To continue pursuing this objective, the application was completely refactored to allow customizability.
 
-### UI
+Part of this refactor was making Data Insights an internal application, no longer relying on an external pipeline. This means triggering Data Insights from the Python SDK will no longer be possible.
 
-### API
+With this change you will need to run a backfill on the Data Insights for the last couple of days since the Data Assets data changed.
 
+### UI Changes
+
+#### New Explore Page
+
+Explore page displays hierarchically organized data assets by grouping them into `services > database > schema > tables/stored procedures`. This helps users organically find the data asset they are looking for based on a known database or schema they were using. This is a new feature and changes the way the Explore page was built in previous releases.
+
+#### Connector Schema Changes
+
+In the latest release, several updates and enhancements have been made to the JSON schema across various connectors. These changes aim to improve security, configurability, and expand integration capabilities. Here's a detailed breakdown of the updates:
+
+- **KafkaConnect**: Added `schemaRegistryTopicSuffixName` to enhance topic configuration flexibility for schema registries.
+- **GCS Datalake**: Introduced `bucketNames` field, allowing users to specify targeted storage buckets within the Google Cloud Storage environment.
+- **OpenLineage**: Added `saslConfig` to enhance security by enabling SASL (Simple Authentication and Security Layer) configuration.
+- **Salesforce**: Added sslConfig to strengthen the security layer for Salesforce connections by supporting SSL.
+- **DeltaLake**: Updated schema by moving metastoreConnection to a newly created `metastoreConfig.json` file. Additionally, introduced `configSource` to better define source configurations, with new support for `metastoreConfig.json` and `storageConfig.json`.
+- **Iceberg RestCatalog**: Removed clientId and `clientSecret` as mandatory fields, making the schema more flexible for different authentication methods.
+- **DBT Cloud Pipelines**: Added as a new connector to support cloud-native data transformation workflows using DBT.
+- **Looker**: Expanded support to include connections using GitLab integration, offering more flexible and secure version control.
+- **Tableau**: Enhanced support by adding capabilities for connecting with `TableauPublishedDatasource` and `TableauEmbeddedDatasource`, providing more granular control over data visualization and reporting.
+
+### Include DDL
+During the Database Metadata ingestion, we can optionally pick up the DDL for both tables and views. During the metadata ingestion, we use the view DDLs to generate the View Lineage.
+
+To reduce the processing time for out-of-the-box workflows, we are disabling the include DDL by default, whereas before, it was enabled, which potentially led to long-running workflows.
+
+### Secrets Manager
+Starting with the release 1.5.0, the JWT Token for the bots will be sent to the Secrets Manager if you configured one. It won't appear anymore in your dag_generated_configs in Airflow.
+
+### Python SDK
+The `metadata insight` command has been removed. Since Data Insights application was moved to be an internal system application instead of relying on external pipelines the SDK command to run the pipeline was removed.