…se parent + relativePath + type

Query metric/plan label change — comparison

Improves the metric/plan name generated for secondary (_lazy / _query) loads so
they relate to their parent/root query, and unifies separators on ..

The secondary lazy name is now always orm.<parent's full name>.<path>.<loadMode>,
so it always prefixes the real parent metric.

Root query name

An explicit setLabel(..) is a short, ambiguous token so it is prefixed with the bean
type (Customer.custMain) for disambiguation. A profile location is already a unique,
type-independent identifier (class + method) so it is used as-is — no bean type prefix.
The bean/entity type is still available downstream as the avaje-metrics type tag.

Secondary lazy (contacts) name

Original prefixes the loaded type (Contact) + the call-site location and uses __
between path and load mode. New prefixes the parent's full name.

Problems fixed

• (A) Secondary load didn't relate to its parent — original prefixed the loaded type
  (Contact) + the call-site location, never the parent query's name. New name literally
  starts with the parent's full name.
• Explicit setLabel was silently dropped for secondary queries when a profile location
  existed.
• __ path/loadMode separator and mixed _/. replaced by uniform ..
• A profile-location root and its secondary loads now use a consistent name (and inline
  SQL comment) — neither is bean-type prefixed, so the secondary is an exact extension of the
  root (e.g. root QOrderTest.run → secondary QOrderTest.run.customer.query).

Nested and .query secondary loads

Each secondary query name is <immediate parent's full name>.<immediate path>.<loadMode>,
so every hop literally prefixes its parent metric. Example with root setLabel("custMain")
on Customer, chain Customer -> orders -> details:

Nested lazy:

orm.Customer.custMain
orm.Customer.custMain.orders.lazy
orm.Customer.custMain.orders.lazy.details.lazy

Secondary eager .query fetch:

orm.Customer.custMain
orm.Customer.custMain.orders.query
orm.Customer.custMain.orders.query.details.query

The intermediate load mode (.lazy. / .query.) is retained so each name is an exact
extension of its immediate parent's name.

avaje-metrics: bean type moved to a tag

Because the new ebean names no longer prefix the queried bean type, the entity is now
surfaced as an avaje-metrics tag instead. ebean.query metrics now carry:

ebean.query{kind=orm|dto|sql, type=<BeanSimpleName>, label=<ebean label>}

The previous type tag (which held the category orm/dto/sql) was renamed to kind,
freeing type to carry the entity name. type is omitted when the bean type is unknown.

This tag is what disambiguates two different-entity queries that happen to share a
profile-location label (e.g. two DB.find(..) calls of different types in one method with
a fixed ProfileLocation). It does so independently of source line numbers, which are not
always present (fetch-group secondary loads and ProfileLocation.create("fixed") have none).

DatabaseMetricSupplier caches the derived Metric.ID by name + bean type (not name
alone), so two plans that share a name but differ by type map to distinct ids/tags rather
than the first one's cached id being reused for the second.

The same applies to a ProfileLocation root (no explicit setLabel). Example with the
finder CustomerFinder.byNameStatus on Customer, chain Customer -> orders -> details:

Nested lazy:

orm.CustomerFinder.byNameStatus
orm.CustomerFinder.byNameStatus.orders.lazy
orm.CustomerFinder.byNameStatus.orders.lazy.details.lazy

Secondary eager .query fetch:

orm.CustomerFinder.byNameStatusQueryFetch
orm.CustomerFinder.byNameStatusQueryFetch.orders.query
orm.CustomerFinder.byNameStatusQueryFetch.orders.query.details.query