RF24: Implement MY_RF24_INVERTED_ACK hack

[nekromant]

This hack allows better nRF24L01<-->SI24R01 interoperability

I have been playing with some of the fakes I got from aliexpress and found out a few ways to properly get them on my existing mysensors network. I have implemented a MY_RF24_INVERTED_ACK define, that comments out RF24_setAutoACK(_BV(RF24_ENAA_P0)). This small edit allows the nodes to work on my network (composed mostly of genuine, or at least better fakes) without an issue.

I have also updated the docs with other tips I've found.

P.S. I haven't tested the 'repeater' feature with this one on, but it should work threoretically

EDIT: Please don't merge it. Found some issues with one of the fakes, will fix it ASAP, perhaps with yet another
workaround

Testing results:

• Some COB fake version from aliexpress, bought a few years ago. This is the only hack that's needed for it to be fully functional on existing mysensors network.
• A newer nRF24L01+ order, package marking "NRF M 24L01+ 2012AB". Doesn't work unless I manually set static Parent ID and Node ID. When it works, I can see tons of "492097 !TSF:MSG:SEND,14-14-0-0,s=1,c=1,t=16,pt=2,l=2,sg=0,ft=0,st=NACK:1" messages. However unlike the COB version it works as a BLe beacon and has no problems connecting with rf24boot bootloader. Turned out to be the 'magic finger' problem as described here: https://ncrmnt.org/2021/01/03/nrf24l01-fixing-the-magic-finger-problem/ None of the modules were working, untill I soldered the 1pF cap.

Signed-off-by: Andrew Andrianov andrew@ncrmnt.org