fix: Respond to the device attributes sequences

[sazary]

resolves #101

this adds handleDeviceAttributes to the wasm patch, and it's implementation is a copy of deviceAttributes function in the main ghostty repo.

for reference, xterm.js returns different values than this but i thought it's better to use ghostty values.

i can confirm that this resolves the fish issue mentioned in the linked issue

[eexwhyzee]

+1 on this, ghostty-web not responding to device attributes queries is also causing nushell to take 2 seconds to start up too:

i applied the WASM patch in this PR on my local build and can confirm that the issue is resolved and nushell starts up appropiately:

[sreya]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[sreya]

Thanks for the contribution ❤️