feat: HasIslands supports nested components

[bruceharrison1984]

This makes a change to the Islands scanning code so that it walks the dependency tree. The current implementation only allows for islands to work if they are directly within the Route. This change allows Islands to be anywhere in the hierarchy.

This PR is more of a working session to try and get this sorted out, because the current implementation is extremely limited and negatively impacts the way users can structure their components. The other alternative is to just always ship the client libraries, but that seems to run counter to why Islands was implemented in the first place.

Current shortfalls:

• Slightly increases transformation time
• Only scans for tsx files

This works was based on conversations from #46

[yusukebe]

Hey @bruceharrison1984 !

I have made changes to 7099fba. Anyway, this PR must be completed. What do you think about my change?

[bruceharrison1984]

@yusukebe Is this also working with alias imports? That was one issue with what currently exists. I think that by using this.resolve, we should be able to get that working as well.

As an opinion, while I realize removing magic-string to reduce dependencies makes sense, it greatly simplifies a lot of operations that are being done currently. It's use is fairly standard in the vite and rollup plugin space. At the end of the day this is your baby, but I just wanted to make my motivations known.

[yusukebe]

@bruceharrison1984

Is this also working with alias imports?

Yeah. I added tests for alias importing. 8612936. It seems to be working! Can you see this again?

[yusukebe]

After merge this, we have to resolve this matter: #105

[bruceharrison1984]

@yusukebe LGTM

Was the only piece I was missing adding the alias to the vite.config.js? I feel like a fool 😄

[yusukebe]

@bruceharrison1984 Thanks!

Land it!