Fix Characteristic and PrimaryService TypeScript declarations to extend EventEmitter

[Copilot]

Characteristic and PrimaryService both extend BlenoEventEmitter (→ EventEmitter) at runtime, but their type declarations in index.d.ts didn't reflect this, causing .on() and other EventEmitter methods to fail autocompletion in TypeScript.

Changes

• Characteristic and PrimaryService now declared as extends EventEmitter
• Added typed on() overloads for all events emitted on Characteristic:

char.on('readRequest', (handle, offset, callback) => { ... });
char.on('writeRequest', (handle, data, offset, withoutResponse, callback) => { ... });
char.on('subscribe', (handle, maxValueSize, updateValueCallback) => { ... });
char.on('unsubscribe', (handle) => { ... });
char.on('notify', (handle) => { ... });
char.on('indicate', (handle) => { ... });

A fallback on(event: string | symbol, listener: (...args: any[]) => void): this overload is also included for custom/unknown events.

[Apollon77]

@copilot There is a validation of the commit message format. Please adhere to it

commit header doesn't match overall header pattern: 'type(scope): message'

(edit the commit you did )

[Copilot]

@copilot There is a validation of the commit message format. Please adhere to it

commit header doesn't match overall header pattern: 'type(scope): message'
...

Commit 5efb03a (fix: Characteristic and PrimaryService TypeScript types extend EventEmitter) is the one that fails validation — it's missing the required (scope). I amended the commit message locally to fix(types): Characteristic and PrimaryService TypeScript declarations extend EventEmitter, but since it was already pushed to the remote, report_progress rebased on top of it rather than replacing it (git detected the amended commit as "already applied" and skipped it).

Without force-push access, I'm unable to rewrite the already-pushed commit history. The latest commit (bb25698) does follow the correct format: chore(types): initial plan for Characteristic EventEmitter inheritance fix.

Could you squash-merge the PR, or force-push with the corrected history? Alternatively, I can explore if there's another workaround available.

[Apollon77]

@stoprocent WDYT?