Fix/executiondata proto pkg

[treethought]

Closes: #???

Description

Fixes the package name for executiondata protobuf file from access -> executiondata.
Related to #1275 and onflow/flow-go-sdk#378 and needed for onflow/flow-go-sdk#417

Previously, with package access, the executiondata types could not be imported in generated go code.

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[koko1123]

Hey this is a good idea because of the access package name overlap, but the intent behind the execution data APi was to be a subset of the Access API. The generated go files will break the flow-go implementation, so we have two possible routes around it:

1. Modify the corresponding handlers in flow-go to avoid copying mutex values
2. re-generate the go files with the older version of buf (in go.mod of this repo)

I suggest making a PR in flow-go for 1., then merging this PR, then updating the flow-go PR with the merged PR hash as a dependency

[peterargue]

I think we should go ahead and make this change before the api is widely used.

@treethought can you pull in master and regenerate the files?

[peterargue]

I'm not opposed to making this change, but I think we should do it as a separate PR.

Are you able to generate the files using the existing setup?

[treethought]

I had added that line for what I used since I couldn't find what version was being used, but just found via #905 (comment) that it seems to be set in the flow-go makefile as v1.3.2

[peterargue]

ah ok. thanks for fixing the docs!

[peterargue]

FYI @nvdtf, @Guitarheroua