...and bump PORTREVISIONs of consumers with hard RUN_DEPENDS

PR: 281470

Included all ports that have USES=java.

PR:	293559

PR:		294036

The maintainer's last activity was a Bugzilla submission in September 2022 about updating py-keras.
No activity of any kind afterwards.

Account of failures to respond spanning for 3+ years (the FreeBSD policy is 3 months) is below.

maintainer timeouts in science/py-tensorflow:
* Jul 1 06:23:34 2025
* Feb 23 05:18:05 2026

unanswered bug reports for science/py-tensorflow:
┌─────────────────────────────────────────────────────────────────────┬─────────────────────────┬───────────────────────┬────────────┬────────────┐
│ Bug                                                                 │ Port                    │ Summary               │ Filed      │ Timed Out  │
├─────────────────────────────────────────────────────────────────────┼─────────────────────────┼───────────────────────┼────────────┼────────────┤
│ #278571 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278571)  │ science/py-tensorflow   │ Update 2.9.1 → 2.16.1 │ 2024-04-24 │ 2025-01-28 │
└─────────────────────────────────────────────────────────────────────┴─────────────────────────┴───────────────────────┴────────────┴────────────┘

maintainer timeout on devel/google-cloud-cpp:
* Aug 1 12:07:51 2023

maintainer timeout on devel/nsync:
* Apr 27 00:50:50 2024

Open Bug Reports with Pending Maintainer Feedback:
 ┌─────────────────────────────────────────────────────────────────────┬──────────────────────────┬────────────────────────────────────┬────────────┬───────────────────┐
 │ Bug                                                                 │ Port                     │ Summary                            │ Filed      │ Awaiting Response │
 ├─────────────────────────────────────────────────────────────────────┼──────────────────────────┼────────────────────────────────────┼────────────┼───────────────────┤
 │ #289001 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289001)  │ devel/google-cloud-cpp   │ Upgrade request                    │ 2025-08-22 │ ~7 months         │
 ├─────────────────────────────────────────────────────────────────────┼──────────────────────────┼────────────────────────────────────┼────────────┼───────────────────┤
 │ #289982 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289982)  │ science/py-tensorflow    │ Doesn't link/symlink its libraries │ 2025-10-03 │ ~6 months         │
 ├─────────────────────────────────────────────────────────────────────┼──────────────────────────┼────────────────────────────────────┼────────────┼───────────────────┤
 │ #294036 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294036)  │ science/py-tensorflow    │ Update to 2.21.0 (patch attached)  │ 2026-03-25 │ 3 days            │
 └─────────────────────────────────────────────────────────────────────┴──────────────────────────┴────────────────────────────────────┴────────────┴───────────────────┘

Ports maintained:
 1. science/py-tensorflow - v2.13.1 (latest: v2.21.0, 8 versions behind)
 2. devel/google-cloud-cpp - v2.27.0 (latest: v3.3.0)
 3. devel/nsync - v1.27.0 (latest: v1.30.0)
 4. devel/crc32c - v1.1.2 (up to date per Portscout)
 5. devel/py-absl - v0.7.1 (latest: 0.15.0, being deprecated)
 6. devel/py-google-pasta - v0.1.7 (latest: 0.2.0)

Approved by:	portmgr@ (policy on inactive maintainers: 3 months is long exceeded)

They must always be bumped after devel/protobuf because it include
following files whose filenames contain %%PORTVERSION%%. Consequently,
the shlib will always change when PORTVERSION is increased.

lib/libprotobuf-lite.so.%%PORTVERSION%%.0
lib/libprotobuf.so.%%PORTVERSION%%.0
lib/libprotoc.so.%%PORTVERSION%%.0

Approved by:	portmgr (blanket; fixing consumers)

With libc++ 21 science/py-tensorflow fails to build, with errors similar
to:

    In file included from tensorflow/tsl/framework/allocator_registry.cc:16:
    In file included from ./tensorflow/tsl/framework/allocator_registry.h:23:
    In file included from ./tensorflow/tsl/framework/allocator.h:28:
    ./tensorflow/tsl/framework/type_traits.h:96:8: error: 'is_signed' cannot be specialized: Users are not allowed to specialize this standard library entity [-Winvalid-specialization]
       96 | struct is_signed<tsl::qint8> : public is_signed<tsl::int8> {};
          |        ^
    /usr/include/c++/v1/__type_traits/is_signed.h:25:8: note: marked '_Clang::no_specializations' here
       25 | struct _LIBCPP_NO_SPECIALIZATIONS is_signed : _BoolConstant<__is_signed(_Tp)> {};
          |        ^
    /usr/include/c++/v1/__config:1167:9: note: expanded from macro '_LIBCPP_NO_SPECIALIZATIONS'
     1167 |       [[_Clang::__no_specializations__("Users are not allowed to specialize this standard library entity")]]
          |         ^

and later:

    tensorflow/lite/kernels/elementwise.cc:245:14: error: no matching function for call to 'EvalImpl'
      245 |       return EvalImpl<float>(context, node, std::abs<float>, type);
          |              ^~~~~~~~~~~~~~~
    tensorflow/lite/kernels/elementwise.cc:192:21: note: candidate function template not viable: no overload of 'abs' matching 'std::function<float (float)>' for 3rd argument
      192 | inline TfLiteStatus EvalImpl(TfLiteContext* context, TfLiteNode* node,
          |                     ^
      193 |                              std::function<T(T)> func,
          |                              ~~~~~~~~~~~~~~~~~~~~~~~~

The former is fixed by https://github.com/openxla/xla/commit/0cead9f,
which unfortunately happened after tsl got split off from tensorflow
into a bunch of separate projects.

The latter is fixed as part of
https://github.com/tensorflow/tensorflow/commit/358119a, but that commit
is quite large. Only the changes to elementwise.cc need to be applied.

PR:		293384
Approved by:	maintainer timeout (2 weeks)
MFH:		2026Q1