Evaluate correct naming for internal clients (which are not drivers)

[dvzrv]

Describe the bug

It seems the (unwritten?) convention about internal clients vs. drivers appears to be, that the drivers have a jack_ prefix and the internal clients do not.
Both types of shared object files usually (on Linux) live below e.g. /usr/lib/jack/.

With jack2 <= 1.9.20 and jack-example-tools we provide jack_inprocess.so, jack_internal_metro.so and jack_intime.so. If these are not in fact drivers, they should be renamed (stripped of their jack_ prefix).

Somewhat related and more of a discussion topic:
Would it make sense to have a specific prefix for all internal clients (e.g. internal_), so that they can be clearly distinguished?

Related issue: jackaudio/jack-example-tools#63

Environment

• JACK Version: 1.9.20 (but the potential inconsistency has been around longer)
• Operating System: Linux
• Installation: n/a

Steps To Reproduce

Build and install jack2 1.9.20 using --example-tools=yes.

Expected vs. actual behavior

It is clear from looking at the list of files in e.g. /usr/lib/jack/ which of them are drivers and which of them are internal clients.