Store Kustomize Binaries in `_output/` Directory for Consistency, Same Like K/K.

[rayandas]

Currently, whenever the developers build the binaries locally, it gets stores inside GOBIN.
However, to align more closely with the practices followed in kubernetes/kubernetes, I suggest that we consider building and storing all Kustomize binaries inside the _output/ directory within the Kustomize repository.

Here's why this change makes sense:

1. Consistency with Kubernetes: Kubernetes follows the practice of storing built binaries inside the _output/ directory within its root repository. This approach helps maintain consistency across the project and makes it easier for contributors and users to find and use the binaries.
2. Simplified Access: Storing binaries in a designated _output/ directory simplifies access for developers. They can easily locate and use the binaries without relying on environment-specific configurations.
3. Clear Build Process: Having a dedicated directory for binaries provides clarity about where to find the output of the build process. This can be particularly helpful for newcomers and those unfamiliar with the project's build conventions.

Adopting this practice can enhance the overall developer experience.

[natasha41575]

Suggestions for this issue:

1. Add a make target at the root of the repo make kustomize to build the binary and store it where you want.

2. (totally optional) It might be helpful to add a developer guide at some point, to whoever picks up this issue, you can start a developer guide if you want, where we just tell people how to build kustomize.

/triage accepted

[rayandas]

/assign