metatag_computed fields create extra values to exports

Here's a patch that uses the MetatagsFieldProcessor for the metatag_computed field as well. While it does get rid of the extra translation exports, it's likely possible that there is some better solution than this one.

Thanks for the patch, I had the same patch and this works nice form me, using D10.1.6 and tmgmt 8.x-1.15.

I think the metatag_computed field should not even be translatable as it is set as computed.
Here is a patch setting computed field as not translatable in ContentEntitySource::extractTranslatableData().

Moves to "Needs work" as it would require a test.

I guess we could even close it as a duplicate of https://www.drupal.org/project/tmgmt/issues/3405309 🐛 Computed fields should not be embeddable fields or source suggestions Needs review if nobody have objection.

Using tmgmt version 1.15 and metatags 2.0.0 and it does not work for me. I can see a lot of "meta" strings to translate

After asking for some channels, pcambra asked me to use both patches in the issue because they are doing differents things. So I can confirm installing both patches fixes the issue.

Missed this issue, we just fixed this in 📌 Exclude read only fields from translation Active