Update build.zig.zon to use the new zig v0.14 version

[zewenn]

The new zig version changed the build.zig.zon file. Not updating to the new standard causes the projects to automatically re-fetch the package on every build (resulting in 10-15 second build times).

I have updated the build.zig.zon to use zig v0.14.0 and the appropriate fingerprint.

[raysan5]

@zewenn thanks for the review!

[10aded]

Great, this closes #4814.

However, per the documentation when creating a package via zig init, it is highly recommended that for security reasons a comment accompany the fingerprint line.

From build.zig.zon when generated via zig init:

// Together with name, this represents a globally unique package
// identifier. This field is generated by the Zig toolchain when the
// package is first created, and then *never changes*. This allows
// unambiguous detection of one package being an updated version of
// another.
//
// When forking a Zig project, this id should be regenerated (delete the
// field and run `zig build`) if the upstream project is still maintained.
// Otherwise, the fork is *hostile*, attempting to take control over the
// original project's identity. Thus it is recommended to leave the comment
// on the following line intact, so that it shows up in code reviews that
// modify the field.
.fingerprint = 0x6f178c1f29db3887, // Changing this has security and trust implications.

The fingerprint line should have the comment

// Changing this has security and trust implications.

I'll submit a pull request with this change soon.

[10aded]

PR made: #4827