GRPC reflection uses plaintext over 443

[mua]

When a https://example.com URL is given for a GRPC call, the client fails with.

error in grpc reflection ReflectionRequestException [Error]: Error: 14 UNAVAILABLE: Connection dropped
    at ClientDuplexStreamImpl.<anonymous> (/home/utku/dev/tds/httpyac/node_modules/grpc-js-reflection-client/dist/GrpcReflection.js:85:24)
    at ClientDuplexStreamImpl.emit (node:events:507:28)
    at Object.onReceiveStatus (/home/utku/dev/tds/httpyac/node_modules/@grpc/grpc-js/build/src/client.js:421:28)
    at Object.onReceiveStatus (/home/utku/dev/tds/httpyac/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /home/utku/dev/tds/httpyac/node_modules/@grpc/grpc-js/build/src/resolving-call.js:129:78
    at process.processTicksAndRejections (node:internal/process/task_queues:85:11)
perform gRPC Request (https://example.com/Service/Method
no protodefinitions found in context

The reason is, while the HTTPS host and port is being used, it tries to connect over 443 without using TLS to get reflection info.