Flow execution logging

Update on the core & ui to log the flow execution on where it was created. The Values that is currently supported for the feature are:

• api - flow was started or ended using the api endpoint. This will also log the user who took the action to call the api endpoint in starting or ending the flow.
• console - flow was started using the command directly in the synQup core’s container. No user will be logged for this value.
• cronjob - flow was started by a cronjob. It is only used by the 'started_by' column. A flow execution will not be ended by the cronjob. If a cronjob is scheduled and a flow execution of this flow is still running, the flow will be enqueued.
• heartbeat - flow was started or ended by the heartbeat system. The only instance that a flow would be started by the heartbeat is when a flow is configured to auto-retry in case of failure, using the feature mentioned below (Auto Retry Failed Flows). The instance that a flow would be ended by the heartbeat is when a flow was killed because of the timeout event that the flow execution was not being update for a certain amount of time.
• process_step - flow was ended by the process step. This value that ended a flow only depicts that a flow has been ended successfully without a problem.

Suggested Feature: This feature needs another future task on all the tables, specially on the CronJob on this topic. Currently, we don’t have an information who created a CronJob that is responsible on starting the flow. So it might be a good feature to also log the creation of cronjobs, flows, users, etc.