Evaluate bpfman-operator actions when a program is added or removed from a BpfApplication

Currently, the Operator returns an error if the user tries to add or remove a program from the program list in a BpfApplication.

If a new program is added to the list after the initial load, it can be loaded separately but will not share the global data with the rest of the programs in the BpfApplication. To allow the sharing, the user would need to first delete the existing BpfApplication, and reload a new one with the added programs.

We could do the unload and reload for the user under the covers, but that may have unintended behavior for the application. In the future, we
may also be able to add more seamless support for incremental loads.

Technically, I think we could support removing a program, but I didn't support that operation to keep the behavior consistent in that you can't change the program list in an existing BpfApplication.

Start by tracing the operator's handling of changes to the BpfApplication program list; no specific files, tests, or entry points are named in the issue. Evaluate the behavior for adding and removing programs, including reloads and global-data sharing, and define the intended behavior before implementation.

Written by the indexing model from the issue text.