Only the first item passed to add_cfe_app_dependency() function is actually registered

[jphickey]

Describe the bug
The add_cfe_app_dependency() function in the build system is intended to register when one module depends on another module. It is supposed to accept a list of modules, but only the first item actually gets registered. If attempting to register more than one, the second item (and anything beyond that) do not have an effect.

To Reproduce
Attempting to change the "BP" app to depend on the bplib library as well as a input/output layer called "iodriver", I changed:

add_cfe_app_dependency(bp bplib)
to
add_cfe_app_dependency(bp bplib iodriver)

However this did not have any effect, I did not get the iodriver public include path as expected - it did nothing.

Expected behavior
All listed dependencies should be registered and public include paths of all dependencies should be added to the app target.

System observed on:
Ubuntu 22.04

Additional context
This is caused by the wrong variable in the loop. There is a loop to handle all the listed dependencies, but it registers the first one multiple times, because the wrong variable is referenced inside the loop.

Reporter Info
Joseph Hickey, Vantage Systems, Inc.