Release bundles using bundle metadata

[bliu-sh]

Currently, bundles are released only by the final destination. This can cause issues for scheduling algorithms that could schedule different routes for bundles in storage that have the same final destination, as bundles could be sent down different routes. For example, consider a scenario with 4 nodes, A, B, C, and D. For two distinct sets of bundles generated at A with final destination D, our scheduler allocates two different routes to ensure deliverability, such as route 1: A->B->D, and route 2: A->C->D. When A->B is executed for route 1, it is possible for bundles originally intended for route 2 to be sent along this route. These bundles may have different requirements that could make them undeliverable if sent to the wrong next hop/contact.

Requested additions:

• The ability to explicitly mark bundles, and release bundles by certain markings.

• And/Or, releasing bundles based on a combination other metadata, such as source, creation time ranges, final destination.

[T-recks]

Resolved in development branch. See Masker class and associated example script.