TPT-2120: Document event and status polling

[zliang-akamai]

📝 Description

Adds user-facing guidance for linodego's asynchronous wait helpers so callers know when to use status polling versus event polling, how to configure poll delay and context timeouts, and which EventPoller constructor fits common create/mutate flows.

• New docs/event_and_status_polling.md covering status waits, event pollers, WaitForEventFinished, WaitForResourceFree, configuration, and practical tips
• README link to the new guide
• AGENTS.md maintenance notes for keeping that file accurate when repo facts change

✔️ How to Test

Documentation-only change. Review the new guide and README/AGENTS links for accuracy against waitfor.go and account_events.go.

# optional: confirm links resolve in-repo
ls docs/event_and_status_polling.md
grep -n 'event_and_status_polling' README.md

[Copilot]

Pull request overview

Adds a new user-facing documentation guide explaining how to use linodego’s asynchronous “wait” helpers, clarifying when to use status polling vs. account event polling and how to configure polling delay and context deadlines.

Changes:

• Added a new guide covering status waits, EventPoller constructors, and lower-level event helpers.
• Linked the new guide from the main README.
• Added explicit maintenance notes to AGENTS.md about keeping repository facts up to date.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
README.md	Adds a link to the new async waiting guide.
docs/event_and_status_polling.md	New guide documenting status polling, event polling, configuration, and usage examples.
AGENTS.md	Adds a “Maintaining This File” section describing when to update AGENTS.md.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

docs/event_and_status_polling.md:286

• This describes the fallback as less precise, but WaitForEventFinished still compares both event.Entity.Type and the normalized entity ID locally for every result (waitfor.go:299-330). Only the server-side filtering optimization changes. Please distinguish efficiency from matching accuracy so users do not infer that unsupported entity types can return another resource's event.

- Entity filtering is optimized for disk, database, linode, domain, and nodebalancer entities. Other entity types may be less precise.