[tpoliaw]

fix: Ignore NameError when introspecting plan functions

When getting type hints to determine if a function is a plan, a
NameError can be raised (specifically when checking pydantic.Field
in this case) and the context loading crashes. Ignoring the error in the
same way that we ignore TypeError allows us to ignore broken types.

As we are only interested in specific return types (Generator) this
shouldn't affect which functions are treated as plans.

Specific symptoms/causes:
In pydantic Field has an argument with a type hint of (via an alias or
two) JsonValue. This is defined as a recursive alias

JsonValue: TypeAlias = Union[int, float, str, bool, None, list['JsonValue'], 'JsonDict']
JsonDict: TypeAlias = dict[str, JsonValue]

when get_type_hints is called on Field a NameError is raised.

This can be seen in a python repl without any blueapi related code

>>> from typing import get_type_hints
>>> from pydantic import Field
>>> get_type_hints(Field)
Traceback (most recent call last):
...
NameError: name 'JsonValue' is not defined

In blueapi, this is a problem if any module included via a PlanSource
has Field as a top level object.

[abbiemery]

Can you elaborate on the comment re pydantic.Field and jsonValue so we don't have to discover this again

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.93%. Comparing base (7622ee0) to head (cb6c788).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1575   +/-   ##
=======================================
  Coverage   95.93%   95.93%           
=======================================
  Files          44       44           
  Lines        3269     3269           
=======================================
  Hits         3136     3136           
  Misses        133      133           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.