Adjust configure.sh to silence another set of protobuf compilation warnings

[mhucka]

Compilation with gcc 15.2 on Debian Linux results in some warnings coming from the Protobuf library:

inlined from 'bool google::protobuf::MessageLite::SerializePartialToZeroCopyStream(google::protobuf::io::ZeroCopyOutputStream*) const' at external/com_google_protobuf/src/google/protobuf/message_lite.cc:411:30:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:33: warning: 'void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int)' specified size between 18446744071562067968 and 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
      |          ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
   30 |                                  __glibc_objsize0 (__dest));
      |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~

This is difficult to address directly, so this PR adds a narrowly-scoped silencing flag to the compilation arguments.

[gemini-code-assist]

Code Review

This pull request modifies configure.sh to add the -Wno-stringop-overflow compiler flag for the protobuf dependency. A review comment correctly identifies that Bazel's per_file_copt option does not support comma-separated flags and will cause compilation errors; the reviewer suggests splitting the flags into multiple configuration lines.