feat: config schema generator

[amrbashir]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[amrbashir]

I am not sure why test-tauri-core fails with this PR when I made no changes to core

[lucasfernog]

You did change it though, I think it's messing with the tauri-utils features. I'll take a look.

[lucasfernog]

The biggest issue is adding the config-schema package to the workspace, which enables the isolation feature for the tauri-utils package even though it's not enabled for the other packages. I think we should find a different way to do this.

[amrbashir]

I could just remove it from the workspace, I mainly added it to the workspace so it can be autogenerated by the IDE's LSP when working with the config.