Implement spatial EnvelopeCombine aggregate translation

[roji]

Closes #28184

[bricelam]

At one point, we couldn’t use == on MethodInfo. Is that no longer the case?

[roji]

This question comes back every now and then :)

I'm not aware of any reason not to (MethodInfo defines its own equality operator), I think we do it quite a lot in the code base. Maybe this is a leftover from some old/weird .NET implementation...

[smitpatel]

#7591

[roji]

Ahh thanks @smitpatel, so it was apparently .NET Native...

[ghost]

Hello @roji!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this

From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.