Allow(optionally) omit activity argument/input in the activity task scheduled event to save the storage cost

Is your feature request related to a problem? Please describe.
The activity input is not really being used for replay. It's mainly for debugging(could be useful for cluster replication as well but can be eliminated/improved if designed properly).

Describe the solution you'd like
Allow workflow to not include argument/input in the actiivty task scheudled event. Just like local activity options: https://github.com/temporalio/sdk-java/blob/806eab71f2b65f762cdd1c4079d3fbad0b62ae1d/temporal-sdk/src/main/java/io/temporal/activity/LocalActivityOptions.java#L58

Describe alternatives you've considered
Using local activity could do that. However, local activity could run into sideffect when it has high failure rate -- the history will get blowed up with many timer events for retry management. (see https://community.temporal.io/t/local-activity-vs-activity/290/3 )

Additional context
This needs server to support because the input is needed to pass to activity task, to activity worker.

Start by tracing the activity task scheduled event through the server path described in the issue, including how its input reaches the activity worker. Determine the scope of an optional omitted input and how retries and replay are affected. Done means workflows can opt out of storing and forwarding the activity input while normal activities continue to work.