I noticed that raising a `BadOutOfRangeError` in a server callback set
through `Server.subscribe_server_callback` resulted in a
*BadInternalError* on the client side (tested with UaExpert) rather than
the expected *BadOutOfRange*. But raising a
`ServiceError(ua.StatusCodes.BadOutOfRange)` instead would show the the
expected *BadOutOfRange* error in the client.
The reason for this idiosyncrasy was that `UaStatusCodeError`s were not
explicitly caught. Therefore the "default" `except Exception` handler
would be used which resulted in a
`ua.StatusCode(ua.StatusCodes.BadInternalError)` to be sent to the
client instead of the actual status code of the error that occurred.

This commit changes the behavior such that the status code of
`UaStatusCodeError`s is respected the same way as it's already done for
`ServiceError`s so that the client correctly receives the status code of
the `raise`d error.

See also https://github.com/FreeOpcUa/opcua-asyncio/discussions/1563#discussioncomment-8382555

This method allows to set a custom setter function on a per-attribute
basis. This setter function will then be called by
`write_attribute_value()` instead of writing the attribute value
directly. This allows for custom logic to be implemented by the user
(such as checking if the value to be written is within a certain range)
and if not, an appropriate error can be raised from that setter,
preventing the write and notifying the client about the occurred error.

* bump cryptography to >40.0.1 in install_requires

* fix syntax

'__name__' -> __name__

'__name__' -> __name__

Fixes a subscription error if there is a space at the end of the identifier value

* Allow List,Union,Optional named fields

Fixes #1441

* use typing