Fluffy generates invalid BasicRadius payloads
``2025-02-24T21:31:38.217876Z  WARN portalnet::overlay::service::ping: Failed to decode custom payload during process_ping: Failed to decode BasicRadius: InvalidByteLength { len: 34, expected: 32 } protocol=State request.source=enr:-Ii4QPImlmeTTQoUjLz9H7GGoamJkg0DzrRuynlOIk0eQAJLPY34TvaXy5hQVyzYJi9nf5JBxddnluILcgN-ll_jh4KCEyJjZoJpZIJ2NIJpcITCISswiXNlY3AyNTZrMaECcenrPmbBCEhI3aCLAHeFo23FTfhVvnbd44xz4MlVAw6DdWRwgiOM`` It looks like fluffy is generating invalid basic_radius payloads? Do you guys implement these test vectors <https://github.com/ethereum/portal-network-specs/blob/master/ping-payload-extensions/extensions/type-1.md#test-vectors>. I need to update the error to print the message received

I am gonna work on a PR to `portal-network-specs` to expose ping extensions to the json-rpc, so we can add tests in hive for this going into the future