Added a method to remove an attribute from a group in EavSetup

[stollr]

Description (*)

The EavSetup class provides methods to add EAV attributes, groups and sets. There are also corresponding methods to remove those records. But there is no opposite to addAttributeToGroup. This commit adds a removeAttributeFromGroup method, which fixes this lack.

An integration test which ensures that the method works, was added, too.

Related Pull Requests

1. This PR depends on Added app isolation attribute to tests in EavSetupTest #39617

Fixed Issues (if relevant)

1. Fixes Add a method to remove an attribute from a group in EavSetup community-features#346

Manual testing scenarios (*)

1. Add a data upgrade setup script with the following content:

$eavSetup = $this->eavSetupFactory->create(['setup' => $setup]);
$eavSetup->addAttribute(Product::ENTITY, 'test_attribute', [
    'type' => 'varchar',
    'label' => 'Test attribute',
    'input' => 'text',
    'required' => false,
    'global' => ScopedAttributeInterface::SCOPE_GLOBAL,
]);
$eavSetup->addAttributeToGroup(Product::ENTITY, 'Default', 'General', 'test_attribute');
$eavSetup->removeAttributeFromGroup(Product::ENTITY, 'Default', 'General', 'test_attribute');

2. Check if the attribute was correctly removed from the group (eav_entity_attribute table)

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @stollr. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.