🐛 Fix go-json generator.

[thylong]

Please provide enough information so that others can review your pull request:

$ go generate ./... generates panic as import paths have changed over time.
This commit free this command execution from panics.

Explain the details for making this change. What existing problem does the pull request solve?

When running $ go generate ./..., the command panics with the following error message :

panic: open <parent_of_fiber_root_directory>/fiber/internal/encoder/vm/vm.go: no such file or directory

goroutine 1 [running]:
main.main()
        <parent_of_fiber_root_directory>/fiber/internal/go-json/cmd/generator/main.go:314 +0x6c
exit status 2
internal/go-json/cmd/generator/main.go:311: running "go": exit status 1

The culprits reside in the filepath.Join() statements in :

filepath.Join(repoRoot(), "internal", "encoder", pkg, "vm.go")
# and
filepath.Join("internal", "cmd", "generator")

# those constructed paths do not exist anymore !

By adding go-json directory in the join statements, the generated paths exists. The generator can now freely write/override the vm.go file 🙂

[efectn]

Thanks.