Blockwise: Allow transfer via NonConfirmable messages (#548)

*Blockwise: Allow transfer via NonConfirmable messages 

Ensured the request type is correctly set during write operations, enhancing reliability and consistency in data handling.


---------

Co-authored-by: Alberto Zambrano <azambrano.etraid@grupoetra.com>
Co-authored-by: Jozef Kralik <jojo.lwin@gmail.com>

Fix issues reported by golangsci-lint

net: implement IsConnectionBrokenError for Plan 9

Enhance Options Buffer for >16 Message Unmarshaling

Previously, the connection was being closed due to unmarshaling failures when
more than 16 options were included in the message. This fix addresses the issue
by increasing the buffer size to accommodate a higher number of options.

Add Request Monitoring Feature to CoAP Connection

The WithRequestMonitor function has been implemented to enable request monitoring for the connection. This function is called for each CoAP message received from the peer before it is processed.

Details of the Feature:

- Functionality: WithRequestMonitor allows developers to implement custom request monitoring logic for incoming CoAP messages.
- Error Handling: If the function returns an error, the connection is closed, providing a mechanism to handle and respond to issues in the monitoring process.
- Message Dropping: If the function returns true, the incoming message is dropped, allowing for selective handling or filtering of messages based on monitoring criteria.

---------

Co-authored-by: Jeff Welder <146992010+jeffwelder-ellenbytech@users.noreply.github.com>

Update UDP: Ensure propagation of control message to pool.Message

This commit enhances the UDP functionality, ensuring proper dissemination
of control messages to pool.Message for improved network coordination
and responsiveness

Fix renovateBot configuration

Upgrade dependencies

Direct:
golang.org/x/exp v0.0.0-20230905200255-921286631fa9
golang.org/x/net v0.15.0

net: Enhance observation management with ETag tracking (#469)

* net: Enhance observation management with ETag tracking

This commit introduces an enhancement to the observation mechanism
in the network module by implementing ETag tracking. The latest ETag
value associated with each observation is now stored in the internal
representation.

With this update, each incoming message containing the ETag CoAP option
automatically updates the ETag value for the relevant observation.
When an observation is canceled, the stored ETag value is utilized.
When the server detects a valid ETag match, it now responds with a
VALID code and an empty payload instead of resending the content
of the resource. This optimization minimizes unnecessary data transfer
and reduces network load.

---------

Co-authored-by: Jozef Kralik <jojo.lwin@gmail.com>

dtls/udp: ensure unique message IDs during reconnections

To prevent collisions during reconnections, it is important to always increment the global counter.
For example, if a connection (cc) is established and later closed due to inactivity, a new cc may
be created shortly after. However, if the new cc is initialized with the same message ID as the
previous one, the receiver may mistakenly treat the incoming message as a duplicate and discard it.
Hence, by incrementing the global counter, we can ensure unique message IDs and avoid such issues.