Attribute type (feed/external) consolidation

As part of our ongoing evolution of the attribute model in Tweakwise, and to support the fact that you can now create new attributes directly in the App (rather than only via feed/external import), we are introducing a streamlined model: the previous distinction between Feed and External attribute types is removed, and both are now treated as one type: Standard. This change simplifies the internal logic and the user experience, and removes legacy distinctions that no longer reflect how attributes are created or managed.

With the ability to create attributes directly in the App (in addition to import), the old notion of Feed vs External no longer mapped cleanly to how customers actually set up attributes. Rather than adding a new type (such as 'App' or 'API'), we simplified logic by merging Feed and External into a Standard attribute. Many parts of our backend logic and UI had special cases (added complexity) for External attributes, which now has been removed. No action is required for users. All existing attributes are migrated behind the scenes: filters, facets and characteristics continue to work as before.

When you see Standard attribute, you now know it covers all attributes created via feed, external feed, API or App. This way the terminology is aligned across UI, API, documentation and internal logic, and lays the groundwork for further advancements without being tied to legacy types.