Consider changing checks for `is std (de)serializer` for `BeanPropertyWriter`

Currently any deserializer/serializer that is not considered Jackson "standard" (de)serializer will lead to de-optimizing access. However, it should really only be necessary to do this for cases where handling would markedly differ:
- `String` (the original reported problem, issue 59 (in old repo))
- `int`/`Integer`
- `long`/`Long`
- `boolean`/`Boolean`

whereas other Object types seem unlikely to have problems due to optimized access.

The reason for being more selective is because there is some cost from de-optimizing; namely additional method call due to chaining, as well as loss of optimization itself.