Release 1.27.0

openvibe-shared/express-async: an async handler's rejection no longer ends the process. Express 4 ignores what a handler returns, so a promise that an async (req, res) => … handler rejects (a database error, a thrown problem) became an unhandled rejection, and Node 22 exits on one. The move to PostgreSQL (ADR-035) made most handlers async; nine services had between 5 and 41 such routes. routeAsyncErrors(app) patches the app's own Express 4 Layer once, so the rejection goes to next(err) and the service's error handler answers, exactly as a synchronous throw always did. Error handlers get the same treatment. On Express 5, which handles promises itself, it does nothing. instrument() calls it, and every service calls instrument(), so a pin bump is the whole change. test/express-async.test.js.