feat(transformer): add objectName+propertyName selector to #fromFunctionQuery

[crysmags]

What does this PR do?

Adds objectName and propertyName fields to #fromFunctionQuery in lib/transformer.js, generating an esquery selector that targets async functions assigned to a specific property on a specific object:

// objectName: 'this', propertyName: '_queryPromise'
AssignmentExpression[left.object.type=ThisExpression][left.property.name="_queryPromise"] > [async]

// objectName: 'conn', propertyName: 'query'
AssignmentExpression[left.object.name="conn"][left.property.name="query"] > [async]

this is handled as a special case because it is a ThisExpression node in the AST, not an Identifier — so it cannot be matched with left.object.name.

Why existing query types don't cover this

The target pattern is an arrow function assigned to an object property inside a function constructor:

function Connection(opts) {
  this._queryPromise = async (sql, values) => { ... }
}

• methodName targets ClassBody > MethodDefinition and Property (object literal) nodes — a different AST shape entirely. Assignment expressions in constructors are not matched.
• expressionName does generate AssignmentExpression[left.property.name="..."] selectors, but without any constraint on the receiver. In files where the same property name is assigned on multiple different objects, this produces false positives and instruments the wrong functions.

objectName + propertyName pins both the receiver and the property, giving a precise match equivalent to what className + methodName gives for class methods.

Usage

// matches: this._queryPromise = async () => {}
functionQuery: { objectName: 'this', propertyName: '_queryPromise', kind: 'Async' }

// matches: conn.query = async () => {}
functionQuery: { objectName: 'conn', propertyName: 'query', kind: 'Async' }

[bizob2828]

@crysmags can you add tests that affect this new behavior?

[crysmags]

Thank you for the review! Ready to merge when you are 🫡

[rochdev]

Why add propertyName? Why not add only objectName and pair it with the existing methodName? Adding propertyName seems like an unnecessary addition to remember and it does the same thing.