Make configuration validation more strict #6216
Description
Is your feature request related to a problem? Please describe.
Started some Accumulo servers processes with that changes in #6207 that removed port search properties. The server processes still had port search properties in the site config. The properties were ignored and nothing complained about them. Site config called this code and I suspect it ignored the port search properties because they had something like a tserver. prefix.
Describe the solution you'd like
Warn on properties that will never be used. Some prefixes in the accumulo config are meant to be extended by user and others are not. Maybe an annotation could be added to prefixes to denote if they can be extended or not. For example the tserver. prefix could have an annotation that specifies it can not be extended and the table.iterator prefix could have an annotation that specifies it can be extended. Probably only need one of the annotations, can treat absence as the opposite.
With this change the code could know that only having the tserver. prefix does not make a property valid.