Fix jsonpath namespace collision by vendoring the full jsonpath engine

[HenkSnavel]

Problem

On Home Assistant core 2026.7 (Python 3.14) the integration fails to set up: the
config flow shows a generic "Unexpected error", and even when an entry loads,
only the handful of non-filter sensors get values.

Root cause is a Python import-name collision:

File ".../enphase_envoy/envoy_reader.py", line 410, in _resolve_path
    result = jsonpath(self.data, path)
TypeError: 'module' object is not callable

jsonpath-python is now pulled in transitively by HA core, and it owns the same
top-level jsonpath import name as the PyPI jsonpath (0.82) package this
integration requires. from jsonpath import jsonpath then resolves to a module
instead of the callable. The two packages cannot coexist.

Why not a small dotted-path shim

A minimal key.key[0] resolver is not sufficient — the endpoint paths rely on
filter expressions, e.g.:

production[?(@.type=='inverters' && @.activeCount > 0)].wNow
consumption[?(@.measurementType == 'net-consumption' && @.state == 'enabled')].wNow

These need the real engine's [?(...)] filtering and flattening semantics.

Fix

Vendor the full Goessner jsonpath 0.82 engine (MIT licensed) in-tree as
normalize() + jsonpath(), and drop jsonpath from manifest.json
requirements. No external dependency, no name collision.

The vendored copy was behaviour-tested 1:1 against the original jsonpath
0.82.2 package across every filter expression the integration uses, so all
existing path strings keep working unchanged.

Notes

• Tested on a live 3-phase Envoy (firmware D8.3.5528, entrez installer token):
  all 44 sensors populate correctly after the change.
• Relates to Fix data fetch breaking on jsonpath namespace collision (TypeError: 'module' object is not callable) #322, which addresses the same collision but with a dotted-path
  parser that does not evaluate the [?(...)] filter expressions, leaving most
  sensors empty.

[mnederlof]

I would suggest putting the vendored jsonpath in a separate file and include that one. then we keep it separate from code we maintain ourselves.

Other than that, great suggestion and thanks!

[HenkSnavel]

Done — moved the vendored engine into its own jsonpath_vendor.py and import it via from .jsonpath_vendor import jsonpath. envoy_reader.py no longer carries the engine. Re-tested the filter expressions against the new module; output unchanged.

[vincentwolsink]

I will first look into just using the library that Home Assistant nowadays imports. At first glance that should not be a problem.

As an alternative we can use the solution proposed here. Thanks.

[vincentwolsink]

#326 and #328