Also test ArvGevSCPSFireTestPacket for auto packet size.

[feuerste]

Some cameras, e.g. the Allied Vision Alvium G1, don't have the GevSCPSFireTestPacket feature, but only the ArvGevSCPSFireTestPacket, so we now test both.

[feuerste]

@EmmanuelP I just saw a comment in e30bdaf about GevSCPSFireTestPacket. I guess my PR does not make sense, as the Arv prefixed version ArvGevSCPSFireTestPacket is only internal to aravis and always available, right? However, the test_packet_check function also uses the prefixed version. With the changes in this PR (basically resulting in the feature check to be always true) the Allied Vision Alvium G1 is able to do automatic packet size adjustments, without it it isn't.
Would you mind to explain what exactly happens with the prefix? Thanks a lot!

[feuerste]

@EmmanuelP I just saw a comment in e30bdaf about GevSCPSFireTestPacket. I guess my PR does not make sense, as the Arv prefixed version ArvGevSCPSFireTestPacket is only internal to aravis and always available, right? However, the test_packet_check function also uses the prefixed version. With the changes in this PR (basically resulting in the feature check to be always true) the Allied Vision Alvium G1 is able to do automatic packet size adjustments, without it it isn't. Would you mind to explain what exactly happens with the prefix? Thanks a lot!

Thinking more about this, would a viable alternative to checking the availability of GevSCPSFireTestPacket be that we entirely remove the check and add a timeout instead, so the auto_packet_size function is not permitted to take more than a second or couple of seconds? So in case of a DMK 23G618, where one test packet takes 300 ms, we would just time out and return the current packet size...

[feuerste]

Closing this in favor of #888.