Fibery integration improvements

> We have been trying to use your fibery mcp through runbear, but have realised that it is quite outdated.
>
> Firstly, it does not support oAuth as the official fibery mcp itself does.
>
> Secondly it hardcodes an internal lookup for fibery/name as the entity title field. But now fibery allows the title field be be renamed, so your assumption breaks the calls with TypeError: Cannot read properties of undefined (reading 'fibery/name')
>
> You can access the official Fibery MCP at https://github.com/Fibery-inc/fibery-mcp-server, which handles this correctly by using the field marked ui/title?: true in the schema, rather than assuming the key is fibery/name.