refactor(coap): fix eslint issues

[JKRhb]

This PR fixes a number of eslint issues in the binding-coap package (also see #586). Due to the fact that are no typescript bindings for node-coap yet some any typings couldn't be removed yet. However, with the next version of node-coap and the merge of #538 this will hopefully also be resolved eventually.

I opened this PR as a draft for now due to some tests that failed locally. The issues should be fixed now :)

[danielpeintner]

Does it make sense to add

// eslint-disable-next-line @typescript-eslint/no-explicit-any

before the any warnings and note down the files in
#534

I know we are somewhat cheating but I guess as long as we keep track of the ignored rules it is fine and we can check from time to time whether more ignored rules can be resolved...

[danielpeintner]

Note: running npm run lint shows 12 warnings.
Maybe it makes sense to switch off @typescript-eslint/no-explicit-any for those 2 files entirely by adding
/* eslint-disable @typescript-eslint/no-explicit-any */ at the top of the file

C:\...\thingweb.node-wot\packages\binding-coap\src\coap-client.ts
   43:20  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   44:36  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   63:38  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   88:46  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  133:38  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  154:38  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  237:97  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\...\thingweb.node-wot\packages\binding-coap\src\coap-server.ts
   36:30  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   36:60  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   36:70  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  200:32  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  200:42  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

✖ 12 problems (0 errors, 12 warnings)

[relu91]

In my understanding, once we have #538 ready to go, we will have also typings for those any variables. So I would keep the warning if you don't really mind. I guess your concerns are for the CI red flags, right?

[JKRhb]

In my understanding, once we have #538 ready to go, we will have also typings for those any variables.

Exactly, I hope that the new version of node-coap is going to be ready soon (unfortunately, the release process is a bit delayed at the moment). Therefore, I would tend to keep the warnings as temporary reminders as well but I can also add the ignore statements if you prefer them, @danielpeintner.

[danielpeintner]

I guess your concerns are for the CI red flags, right?

Yes :-)

Either way is fine!

[JKRhb]

I now added a commit for explicitly ignoring the anys which can hopefully be removed soon :)

[danielpeintner]

I now added a commit for explicitly ignoring the anys which can hopefully be removed soon :)

Thanks, I added it to #534