feat: Settings page for the log path + poll interval

[GabrielBBaldez]

Today the plugin auto-detects the first errors-ai.log in the project and polls on a fixed interval. Add a small Settings page so a user can point it at a specific file and tune the poll — useful in multi-module projects or when the log lives under build/.

What to do

In the :plugin module:

1. Add a PersistentStateComponent (project-level) holding two fields: logPath (empty = auto-detect, the current behavior) and pollSeconds (default = whatever StacktalePanel uses today).
2. Add a Configurable (registered via <projectConfigurable .../> in plugin.xml, under a "Stacktale" entry) with a text field for the path and a spinner for the interval.
3. Make StacktalePanel read these: if logPath is set, use it; otherwise keep auto-detecting. Apply pollSeconds to the existing poll.

Keep the defaults exactly matching today's behavior so existing users notice nothing until they change a setting.

How to verify

./gradlew runIde, open Settings → Tools → Stacktale, set a path, and confirm the tool window reads that file; clear it and confirm auto-detect returns. ./gradlew test green.

Files: a settings state class + a Configurable under plugin/src/main/java/.../idea/, plugin.xml, and a small change in StacktalePanel.

[kycasdzxc]

Picking this up👍

[GabrielBBaldez]

Assigned to you — sorry for the long silence, that one's on me.

If you're still up for it, one thing that isn't obvious from the issue text. StacktalePanel polls like this:

private static final int POLL_MILLIS = 3000;

private void schedulePoll() {
    alarm.addRequest(() -> {
        ...
        schedulePoll();          // re-arms itself
    }, POLL_MILLIS);
}

Since each tick re-arms the next one, read the interval from the state component inside schedulePoll() rather than capturing it once when the panel is built. Capture it once and the setting appears to do nothing until the tool window is closed and reopened — which looks like a bug to whoever changes it, and it's the kind of thing that slips through a manual test because you usually restart anyway.

Same shape for logPath: empty should keep today's auto-detect, so the detection stays the fallback rather than getting replaced.

And if you've moved on to other things, that's completely fine — just say the word and I'll unassign so it's free for someone else. No hurry either way.

If the plugin turns out to be useful to you, a ⭐ on the repo helps more than you'd think — it's mostly what decides whether anyone else finds it.