Pass `field` context as third argument to `matchFieldOptionValue()`

### Please avoid duplicates

- [X] I checked [all open feature requests](https://github.com/gr2m/github-project/issues?q=is%3Aissue+is%3Aopen+label%3Afeature) and none of them matched my problem.

### What’s missing?

The current `matchFieldOptionValue` constructor options receives two arguments

```js
function (fieldOptionValue, userValue) {
// return true or false
}
```

I suggest we pass a 3rd `context` argument

```js
function (fieldOptionValue, userValue, context) {
// return true or false
}
```

`context` would look like this

```js
{
field: {
name: "My Field",
userName: "myField",
// maybe also `type`, and `options`, but we could add that later
}
}
```

That way we could add more context in future, e.g. `project`, which would be the current project instance.

### Why?

The way options are matched might differ depending on the field

### Alternatives you tried

:shrug

### Would you be interested in contributing the feature?

- [ ] yes

Busca en el repositorio `matchFieldOptionValue()`, sus opciones del constructor y sus puntos de llamada. Rastrea cómo llegan los datos del campo al matcher y, después, define y pasa el objeto `context.field` propuesto sin romper los callbacks existentes de dos argumentos. Se considera terminado cuando el matching dependiente del campo puede leer el contexto del campo y las pruebas existentes relevantes siguen pasando.

Escrito por el modelo de indexación a partir del texto del issue.