Remove executable bit on .json files and exclude script file from published crate

[LeChatP]

Hello,

I’m currently working on packaging your crate for the Debian repositories, and I noticed a couple of small issues that cause problems during Debian’s checks:

• The following .json files in the crate are marked as executable :
  1. data/github_events.json
  2. data/instruments.json
  3. data/mesh.json
  4. data/mesh.pretty.json
  5. data/random.json
• The fuzz.sh should not be shipped inside the crate

Both of these raise linting issues on the Debian side, and ideally the crate would ship without them.

Would you be open to:

1. Removing the executable bit from all .json files,
2. clean your published crate on crates.io by excluding the script from the crate via the exclude field in Cargo.toml
3. Publishing a new release on crates.io with these fixes?

That would make the crate much easier to package downstream, and help get it into Debian smoothly.

Thanks a lot for your work on this project!

[Licenser]

Heya, absolutely at least 1 and 2 are super easy :) let me double check with other contributors regarding 3 since we're right now in the process of a release with breaking changes so we want to make sure we bundle everything that's icky together :D

[Licenser]

thanks to @Sylfrena it's done :) released as 0.16