Plugins conflict when there is no actual conflict

# Bug Report

## Plugins conflict when there is no actual conflict:
i created two plugins A and B
A: has a config-file tag that adds two activity tags to the application tag.
B: an edit-config that adds attributes to the application tag.

when i add B and then A no issue
when i add A and then B (i need this because i've created a cordova app starter that has the A plugin by default),
it says there's a conflict that actually doesn't exist but no problem i tried to force the command
the first activity tag added by the A Plugin is being removed which crushes the A plugin

### What is expected to happen?
the B plugin should be added with no probs at all;
no need to force at all because there is no actual conflict.
or fix the conflict detection algo.
thank you

### Version information
Cordova-android: 10.1.2
cordova-cli: 11.0.0
windows 10

## Checklist

- [x] I searched for existing GitHub issues
- [x] I updated all Cordova tooling to most recent version
- [x] I included all the necessary information above

The report provides no repository file, test, or entry point to start from. Reproduce the plugin order described with Cordova Android 10.1.2 and CLI 11.0.0, then trace conflict detection and forced plugin application; done means adding B after A reports no conflict and preserves both activity tags.

Written by the indexing model from the issue text.