Deserializing error for string type

Nobody has claimed this yet.

**Describe the bug**
String types in service types cause microROS on the MCU side to fail in the executor due to a deserializing error. Running it through a debugger it fails in ucdr_deserialize_sequence_header when parsing the nested message type.

Service calls with non-string types work as expected. I've verified it's not a buffer overflow since the buffer size >> bytes received. There is also no packet corruption in UDP traffic, the dest packet and src packet match 1:1.

**To Reproduce**
Steps to reproduce the behaviour:
1. On MCU, init service with service type that has a string type
2. On host side, call service

**Expected behaviour**
The MCU accepts the service call and handles accordingly.

**Actual behaviour**
Executor fails due to deserialization error.

**System information (please complete the following information):**
- OS: Ubuntu 22.04
- ROS 2 Humble
- MCU: STM32F767ZI

Reproduce the service call on the STM32F767ZI with a string field using ROS 2 Humble, then inspect the executor failure at ucdr_deserialize_sequence_header while parsing the nested message type. The issue is done when the MCU accepts and handles the service call without a deserialization error, while non-string service calls continue to work.

Written by the indexing model from the issue text.