[apex] ApexCRUDViolation incorrectly cleared when SOQL directly populates a Map

Affects PMD Version:
7.0.0-rc3

Rule:
ApexCRUDViolation - https://pmd.github.io/pmd/pmd_rules_apex_security.html#apexcrudviolation

Description:
PMD incorrectly does not report the need for validation of CRUD permissions before SOQL SELECT statements that directly populate Map objects.

Code Sample demonstrating the issue:

This method queries data and directly populates a Map object and no CRUD validation error is shown (incorrect):

public Map<Id, Account> myMethod()
{
    Map<Id, Account> accountMap = new Map<Id, Account>([SELECT Id, Name FROM Account]);
    return accountMap;
}

This method also queries data but doesn't populate a Map - PMD does report a CRUD validation error (correct):

public List<Account> myMethod2()
{
    List<Account> accounts = [SELECT Id, Name FROM Account];
    return accounts;
}

Expected outcome:

PMD should report a violation when doing a SOQL SELECT statement directly into a Map object.

Running PMD through: VSCode using https://marketplace.visualstudio.com/items?itemName=chuckjonas.apex-pmd (v0.6.2)

Start with the ApexCRUDViolation rule and reproduce the two SOQL examples from the issue, comparing the Map assignment with the List assignment. Done means the rule reports a CRUD validation violation for a SOQL SELECT that directly populates a Map, while preserving the existing behavior for the List case.