fix: always notify if revocation notification record exists

[TimoGlastra]

Removes the check to notify in the on_revocation_published event handler. This check in the on_revocation_published would only take the global config option into account, meaning it doesn't matter if you provided notify: true in the /revoke endpoint.

ARevNotificationRecord is only created if a notification should be sent (either global agent config, or notify prop in the revoke endpoint). So if a record exists I think we can assume that a notification should be sent as otherwise the record wouldn't exist in the first place. Maybe I'm missing something?

https://github.com/hyperledger/aries-cloudagent-python/blob/681e9aab9a6f6d3e76484d02ccb969d3227bf34f/aries_cloudagent/revocation/manager.py#L116-L126

[codecov-commenter]

Codecov Report

Merging #1665 (1f8453c) into main (535f14e) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1665      +/-   ##
==========================================
- Coverage   95.50%   95.50%   -0.01%     
==========================================
  Files         528      528              
  Lines       32738    32736       -2     
==========================================
- Hits        31266    31264       -2     
  Misses       1472     1472              

[dbluhm]

Away from a computer ATM so not the most thorough of reviews but the changes look good and reasoning seem reasonable :)