Fix field item type tag (#16860)

# Introduction
This has been fixed on main already 1 hour ago, this PR now only passes
the field application id instead of the object applicationId that could
be different for example when creating a custom field on a standard
object

For the moment not introducing any logic around application integrity
directly and still relying on the isCustom and standardId definition
This will have to be refactored once we deprecate the standardId

packages/twenty-front/src/modules/settings/data-model/utils/getItemTagInfo.ts

@@ -27,10 +27,10 @@ type ManagedItemTagInfo = {
 };
 
 export const getItemTagInfo = ({
-  objectMetadataItem: { isCustom, isRemote, applicationId },
+  item: { isCustom, isRemote, applicationId },
   workspaceCustomApplicationId,
 }: {
-  objectMetadataItem: {
+  item: {
     isCustom?: boolean;
     isRemote?: boolean;
     applicationId?: string | null;