docs: Documented need of solana kit with framework-kit

[ddddsssss4]

Summary

• Documented the relationship with @solana/kit in the root README to explicitly explain the dependency structure.
• Clarified the architectural decision to not re-export Kit primitives to ensure separation of concerns and prevent "wrapper confusion."
• Added an Interop Example code block demonstrating the intended usage pattern: importing primitives (like address) directly from @solana/kit while using hooks from @solana/react-hooks.

Testing

• pnpm lint
• pnpm test
• pnpm build
• Other (describe):

[GuiBibeau]

Even if i put something like this in the issue, i think we don't have to be explicit about it or name other libraries in there.

I like the separation of concerns bullet points bellow! I think the intro text should simply state the approach maybe a bit like this

Suggested change

	We want to avoid the "wrapper confusion" often seen in earlier libraries (like Gill), where it was unclear whether developers should use the framework's version of a type or the native version.
	Framework-kit is built on top of `@solana/kit`. As such, types from Kit are compatible with Framework-kit.

[GuiBibeau]

do we have a way to show where the types converge? For example

import { useWallet } from '@solana/react-hooks'
import { address, type Address } from "@solana/kit";

export const MyComponent = () => {
const wallet = useWallet();

 // wallet.session.account.address is of type Address
}

This is likely not the example to give but the whole type system of framework-kit is built on top of @solana/kit we should give an example of mixing the two libraries where the types converge

[ddddsssss4]

Hey thanks for feedback, I’ve updated the sections you highlighted. Please let me know if you'd like any further refinement.