Plugin-Client config.ts being hardcoded kills configurability.

[GKNewsrooms]

We have resorted to patching https://github.com/kubb-labs/kubb/blob/main/packages/plugin-client/templates/config.ts using npm patch-package. I have already gotten one pull request on making it better merged, but there isnt a one size fits all implementation for buildFormData. This should be overridable in the client import path or somewhere else

overall buildFormData being inside of the config.ts is a huge mess. Why does it get copied to the main generated/.kubb directory? it should be self contained to the plugins should it not? Also seems a lot of things point to it.

[stijnvanhulle]

@GKNewsrooms We don't want to include Kubb logic and imports inside a code base (only dev Deps needed for Kubb) that is why we copy config.ts to the .kubb folder. What we could do here is have one file that contains everything, this mean you can override the logic with importPath. Thoughts?