feat: plugin t-function-matcher should support customizing the t-function name

[KraXen72]

currently, it's hard-coded to t. Please add an entry to PluginOptions to configure the t-function, so it properly replaces it when extracting using sherlock.
I have attempted to make this modification myself, however, I couldn't get the plugin to build after running pnpm install (which took 24 minutes!)
Thanks!

[felixhaeberle]

I'll move this to a discussion as it's not our top priority to change the t function matcher. It would make more sense if people just aligned with the standard behavior or created a new matcher if that makes sense (e.g., complete other syntax).

If more people decide this would be helpful, we consider it again.:)

[KraXen72]

in the codebase i'm working on, it's basically the exact same as default t-function matcher, it's just re-exported as translate for better code readabililty / maintainance:

not having the ability for the t-function matcher to customize this, and thus half of sherlock not woking (the inline keys are not showing, as is not the detection of strings without a translated equivalent), really hinders the experience, for what could be a simple patch to the t-function matcher.
As I mentioned in discord, I attempted to modify and contribute to the t-function matcher plugin, however, 1) the pnpm install of the plugin itself took over 20 minutes 2) it still didn't work due to not having all other packages it depends on installed. That's the reason why I created this issue - someone from inlang who has it already set up on their machine could take care of it in a matter of minutes.

I would be really glad if you re-considered adding the option to customize the t-function matcher plugin function name.