Ingestion: Allow users to input SSL config instead of providing paths

[ayush-shah]

Instead of asking users to add SSL file path for CA, Certificates and Keys, instead we ask users to provide content of the same, we generate a temp file with that content and run the ingestion with that temp file's path as part of the config. This way, if the user has some restrictions on uploading of the file, it works with the input.

[harshach]

@ayush-shah can you add some context where this needs to be done?

[pmbrull]

@ayush-shah moving this to 1.4. It is similar to https://github.com/open-metadata/OpenMetadata/issues/14107 and we need to figure out the right way of how to get this working on SaaS as well

[metalshanked]

This will be boon for sure especially for K8s where this needs mounting and additional steps

[ayush-shah]

UI

• Upload & Read
• Send to backend

Backend

• Store as secret ( by default as per json schema )

Ingestion

• Fetch Secret from API, Create temp file for the secret , use it through the process, delete at the end