Organization enrichment frontend

[joanagmaia]

Changes proposed ✍️

What

🤖 Generated by Copilot at 156df5d

This pull request adds a feature to enrich organization data with additional attributes and display them in various components. It modifies the organization-model.js, build-api-payload.js, and settings-pricing-plans.js files to support the new feature. It also creates new components such as AppOrganizationFormAttributes, AppOrganizationHeadline, and AppOrganizationAsideEnriched to show the enrichment data in the organization form, view, and list pages. It updates the existing components such as organization-list-table.vue, organization-view-aside.vue, and organization-view-header.vue to enhance the layout and functionality. It adds a new utility function isValidUrl in the string.js file to validate the profile urls.
​

🤖 Generated by Copilot at 156df5d

We are the masters of data, we enrich the organizations
We filter and sort them by attributes and relations
We display them in forms and tables, we edit them with ease
We are the pro plan users, we pay the highest fees

Why

How

🤖 Generated by Copilot at 156df5d

• Add new components to display organization enrichment attributes in various layouts (link, link, link, link)
• Modify existing components to render organization headline, description, and enrichment attributes in the organization list table, form page, and view page (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
• Add new fields and options to the organization model and the form model to support the enrichment attributes (link, link, link, link, link, link)
• Add a new file to export the enrichment attribute objects and types (link)
• Add a new feature to the pro plan to indicate the number of organization enrichments per month (link)
• Modify the filter helper function to support the lastEnrichedAt field in the filter panel (link)
• Add a new utility function to validate the profile urls (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.