fix: #3607228 Drop the share button that a recipe cannot create

webshare.settings carried an Instagram share button that can never appear, so this takes it out and closes the weights behind it.

Why it could never work. webshare_install() calls _webshare_migrate_default_platforms(), which reads webshare.settings buttons and inserts one row per button into the webshare_platforms table. That runs when the module installs, and webshare is installed by varbase_blog_base / varbase_events_base — dependencies applied before this recipe's config actions. The action therefore always lands after the seed, and no row is ever created. On a clean install the table holds linkedin, facebook_share, x and the disabled defaults, and the rail renders three icons.

Two further points, so this is not revisited:

• Default content cannot do it either. The module declares no entity type at all — no config entity, no content entity, only PlatformForm writing straight to a schema table. Default content ships entities, so there is nothing for it to create.
• Even a seeded row would not share. The seeder takes its URL from webshare's own $default_templates, which has no Instagram entry, because Instagram has no share endpoint. The row would get an empty url_template, and webshare treats that as a copy-to-clipboard button — an Instagram icon that copies the URL.

Instagram stays where it belongs and already works: the footer, from default content, as a follow link.

The Webshare side of this is not yet filed: that project's issue queue is currently disabled on drupal.org, so the report is written but cannot be submitted. It asks for platforms to be declarable from configuration — a config action, a re-sync, or platforms as config entities.

AI-Generated: Yes

Checkpoints:

• File an issue
• Addition/Change/Update/Fix
• Testing to ensure no regression
• Automated unit testing coverage
• Automated functional testing coverage
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release