Replace sentinel arguments and return values with std::optional

[jhale]

Describe new/missing feature

std::optional provides a modern way to express passing or returning value or not computed.

We are currently using many sentinel function arguments and return values including -1, nullptr and empty strings that require the user to read the docstring of the function to understand the argument or return value. These can be replaced with std::optional which is very explicit. An additional advantage is that nanobind has support for std::optional which results in consistent behaviour between the Python (typing.Optional) and C++ interfaces and a reduction in Python wrapper code complexity.

A first step would be identifying all typing.Optional arguments in Python which typically leads to a sentinel in C++.

Examples of use are here:

#3328
#3322

Suggested user interface

No response

[schnellerhase]

• set_bc: make $x_0$ optional (this will require some more changes, but should be able to remove a quite drastic code duplication problem) (see Use std::optional to reduce code duplication in boundary condition setting #3434)
• locate_entities_boundary and exterior_facet_indices combinable - see Favor exterior_facet_indices over locate_entities_boundary for retrieving complete boundary #3283
• (locate_dofs_topological)