Allows storing execution history in S3 or fileSystem

The idea is:

It is a poor design to store large amounts of JSON data related to execution records in a database when the execution count is very high. Metadata and execution data should be separated.

My use case:

When the workflow transmits large amounts of JSON data and executes frequently…