Bug: Accordion using dynamic tabs and :multiple="true" keep incorrect tabs expanded when changed

[ched-dev]

I'm submitting a ... (check one with "x")

[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primevue/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=110

CodeSandbox Case (Bug Reports)
Bug behavior is reproduced at https://codesandbox.io/s/dreamy-architecture-mbej6m?file=/index.html

Current behavior
When I have an Accordion with :multiple="true" using dynamic tabs, the tab will stay open by index instead of keeping state with specific item.

Expected behavior
I expect the accordion to keep items open by the specific item instead of index. This is because if I add a new item, I want each item to keep its state.

Minimal reproduction of the problem with instructions

1. Expand the first item in the Accordion
2. Click the Add Tab button
3. The first tab will remain open even though the item has changed

https://codesandbox.io/s/dreamy-architecture-mbej6m?file=/index.html

Accordion.Bug.mov

What is the motivation / use case for changing the behavior?
We use the Accordion to show a list of events. When a new event occurs, we add the event as a new tab. If a tab was open at a specific index, it will now display it's open state based on it's new index, not the specific item.

Please tell us about your environment:
See codesandbox environment

• Vue version: 3.X
  Vue@next via unpkg script src

• PrimeVue version: 3.12.X
  Version 3 via unpkg script src

• Browser:
  Chrome 100.0.4896.127 Mac OS 12.0.1

[tugcekucukoglu]

activeIndex can be controlled when a new tab is added. Please check this example

[ched-dev]

I still think the expected behavior when using :multiple="true" is that open tabs stay open and a new tab can start closed. I know you can add code to make that happen, but the default behavior right now feels like a bug. I shouldn't have to add code to "fix" the behavior.