Create final tag for ccpp-prebuild and freeze/remove the code?

[climbfuji]

Description

At this point, we are all committed to moving away from ccpp-prebuild.

Solution

We should consider creating a final tag of the current develop branch, adequately named, and then freeze the ccpp-prebuild.py code. At the same time, we should set a date for the removal of the code - or maybe remove it right away. Folks who need to use ccpp-prebuild.py because they are not yet ready to transition to capgen should use the tag.

Alternatives (optional)

Do nothing.

Related to (optional)

capgen unification

[climbfuji]

I created the following tag for NEPTUNE: neptune_20260428_ccpp-prebuild_final

commit b0f9673b22868490195e5d6e4f5b9bafaeffeaf1 (HEAD -> develop, tag: neptune_20260428_ccpp-prebuild_final, origin/develop, origin/HEAD)
Author: Dom Heinzeller <dom.heinzeller@icloud.com>
Date:   Tue Apr 28 15:06:12 2026 -0600

    Cleanup: remove unused directories logging/* and stub/* (#738)

    Cleanup: remove unused directories `logging/*` and `stub/*`