vector serialization does not take into account endianness

The [gRPC protocol is defined](https://github.com/ansys/api-eigen-example/blob/108085fcaa860a9d1e27abbdc561c160a98e09e3/src/ansys/eigen/protos/grpcdemo.proto#L21) as sending over the bytes of arrays directly, but does not take into account endianness. This means the protocol will fail spectacularly (type 3 error, bad data with no error) if the client and server machines have different native endianness.

https://github.com/ansys/api-eigen-example/blob/108085fcaa860a9d1e27abbdc561c160a98e09e3/src/ansys/eigen/cpp/grpc/client/src/GRPCClient.cpp#L499

https://github.com/ansys/api-eigen-example/blob/108085fcaa860a9d1e27abbdc561c160a98e09e3/src/ansys/eigen/python/grpc/client.py#L280

Unless there is another reason, I recommend using gRPC arrays instead of bytes. gRPC can handle this for us.

从引用的 grpcdemo.proto 定义以及 src/ansys/eigen/cpp/grpc/client/src/GRPCClient.cpp 和 src/ansys/eigen/python/grpc/client.py 中的序列化位置开始。将当前基于 bytes 的表示与 gRPC 数组进行比较，并确定必须保留的跨字节序行为。当具有不同本机字节序的客户端和服务器能够交换向量数据而不会发生静默损坏时，即视为完成。

由索引模型根据 Issue 内容生成。