Pass `inputs` through to Result class

I would like to be able to access a tasks inputs when reading/writing results. This allows properly caching based on the different inputs to a function, for example by templating a filename as experiment;m=5.

Current behavior

Please describe how the feature works today The prefect.context is passed to the read/write(exists?) methods of the Results class

Proposed behavior

Please describe your proposed change to the current behavior Please pass the inputs also.

Example

Please give an example of how the enhancement would be useful This would allow something like the following

@task(result=GCSResult(bucket='bucket', location='{task_name};m={inputs["multiplier"].txt'))
def experiment(multiplier=1):
    # do something
    return

[joshmeek]

@marwan116 Yes it will be!

[cicdw]

Hi @pedromachados : target is a keyword you should only use if you intend to affect the way the pipeline runs as described above. target and location are mutually exclusive at the task level, and if both are provided target will be used.