fix(native): Fix build-time warnings with C++ builds

[mujacica]

• Fix build-time warnings with C++ builds

---

Summed size of utsname fields could be larger than the 256 bytes we allow for the csd_version string. (see linux/sysname.h`). Thus we increase the size to fit these fields.

_deps/sentry-build/CMakeFiles/sentry.dir/src/transports/sentry_http_transport.c.o
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/transports/sentry_http_transport.c: In function ‘retry_send_cb’:
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/transports/sentry_http_transport.c:258:37: warning: missing braces around initializer [-Wmissing-braces]
258 | sentry_client_report_t report = { { 0 } };
| ^
| { }
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/transports/sentry_http_transport.c: In function ‘http_send_task’:
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/transports/sentry_http_transport.c:305:37: warning: missing braces around initializer [-Wmissing-braces]
305 | sentry_client_report_t report = { { 0 } };
| ^
| { }

/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/backends/native/minidump/sentry_minidump_linux.c: In function ‘write_system_info_stream’:
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/backends/native/minidump/sentry_minidump_linux.c:526:62: warning: ‘%s’ directive output may be truncated writing up to 64 bytes into a region of size between 61 and 253 [-Wformat-truncation=]
526 | snprintf(csd_version, sizeof(csd_version), "%s %s %s %s", uts.sysname,
| ^~
527 | uts.release, uts.version, uts.machine);
| ~~~~~~~~~~~
/home/runner/work/teapot/teapot/build/debug/_deps/sentry-src/src/backends/native/minidump/sentry_minidump_linux.c:526:9: note: ‘snprintf’ output between 4 and 260 bytes into a destination of size 256
526 | snprintf(csd_version, sizeof(csd_version), "%s %s %s %s", uts.sysname,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
527 | uts.release, uts.version, uts.machine);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[JoshuaMoelans]

do we need the full 512 or is this a bit overkill (since we know it to be upper-bounded by 260, maybe we just take the next largest size divisible by 8)

Suggested change

	char csd_version[512] = "";
	char csd_version[264] = "";