feat: add useSse hook

[meet-student]

[中文版模板 / Chinese template]

🤔 This is a ...

• New feature
• Bug fix
• Site / documentation update
• Demo update
• TypeScript definition update
• Bundle size optimization
• Performance optimization
• Enhancement feature
• Internationalization
• Refactoring
• Code style optimization
• Test Case
• Branch merge
• Other (about what?)

🔗 Related issue link

• close 有没有封装sse的hook？ #2690

💡 Background and solution

📝 Changelog

Language	Changelog
🇺🇸 English	add useSse hook
🇨🇳 Chinese	add useSse hook

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pkg-pr-new]

npm i https://pkg.pr.new/ahooks@2826

npm i https://pkg.pr.new/@ahooksjs/use-url-state@2826

commit: ba24b6e

[chris-mo]

I would use this immediately!

One question/concern:
EventSource cannot set custom headers (see the WHATWG SSE spec), so a useSse that only wraps it cannot send Authorization or support POST. Could we treat EventSource as the default transport, but not the only one? if headers (or method/body) is set, use fetch + ReadableStream (or @microsoft/fetch-event-source) and keep the same event/data/id parsing. Alternatively, accept an injectable factory (getEventSource / custom fetch) so callers can plug in a headers-capable polyfill.