misc/58365: base32/base64/debug32/debug64 are unmaintainable and unnecessary

[campbell+netbsd%mumble.net@localhost]

>Number:         58365
>Category:       misc
>Synopsis:       base32/base64/debug32/debug64 are unmaintainable and unnecessary
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 25 01:35:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetBSD32 Flistation
>Environment:
>Description:
The base and debug set lists have perfectly good compatdir/compatfile tags which were previously used to automatically generate set lists for MKCOMPAT=yes builds.

Now, all of the entries that were previously automatically generated are manually written in each of the base32/ad.*, base32/md.*, base64/ad.*, debug32/ad.*, debug32/md.*, and debug64/ad.* set lists.  Which need to have exactly the same _other_ tags, like gcc=12, kerberos, pam, whatever, to match MK* flags.  But invariably these are inconsistently updated.

None of this should be necessary.  The compat sets should be derived from the existing compat-tagged set list entries, not manually maintained.
>How-To-Repeat:
use any non-default build options with MKCOMPAT=yes, like build.sh -c clang
>Fix:
Two options:

1. adapt the automatic logic in sets.subr to generate the new base32/base64/debug32/debug64
2. revert all the base32/base64/debug32/debug64 set changes and deal with the motivating problem another way