Investigate more generic handling of `queryName` field in QueryBuilders

[cbuescher]

Working on #10669 the issue came up that most of the queries implementing "QueryBuilder" can be named queries supporting the _name parameter and also have internal queryName field. When constructing the actual lucene query this is used to store the resulting named query in the QueryParseContext. We should try to think about a more generic way to handle this for all queries.

From the 37 queries currently implementing QueryBuilder only 7 don't support having a "queryName":

• BoostingQB
• ConstantScoreQB
• FunctionScoreQB
• MatchAllQB
• SpanMultiTermQB
• TemplateQB
• WrapperQB

[dakrone]

I think all queries should support _name for the sake of completeness

[clintongormley]

agree with @dakrone - if a query doesn't support it, it's a bug

[javanna]

+1 on supportong _name across the board. As part of the query refactoring we should indeed make this more generic, to make sure we don't forget about it for some queries.

[javanna]

I think we should do the same with boost rather than repeating it for every query. We should support boost across the board too no?

[javanna]

Closed via #11974