Bug fix for max used num check for non-primary used frontend

The issue was that when re-assigning frontend resource (through
reclaiming) to a different client, max used number check was not done
for the frontend resources that were not inprimary use and simply
blocked as used due to exclusive group management.

Bug: 300557208
Test: atest TunerTest
Change-Id: I34a1368c39b48d765f5fcd3e9d3fccb5820fc8c9