automatically set some PIP bits

[balazsracz]

Some binaries built with openmrn have different capabilities even from the basic set.
THis happens with the arduino environment especially, where there might be no configuration space, no CDI, no ACDI, etc.

We should auto-detect what capabilities exist based on the constants like SNIP_DYNAMIC_FILENAME, CDI_FILENAME, CDI_DATA, etc. and compute the appropriate PIP capabilities bits. This would avoid having users gets into a CDI screen that does not have an XML behind it.

Similarly with firmware upgrade protocol (somehow figure out a way whether enter_bootloader() is implemented or not).

[atanisoft]

Perhaps we should define a set of constants with default setup to be disabled out-of-box for optional features (CDI, ACDI, etc) and provide easy overrides for them. I don't think we need to be fully automated here, especially in the Arduino environment where it can vary wildly. We can augment the examples to provide default overrides based on the example configurations though.