Sync with standalone developments and options for the LSTOutputConverter

[VourMa]

This PR includes the following developments:

• BuildFile clean-up
• Uses the TrackCandidate type to determine the LST objects in CMSSW.
• The option to create TrajectorySeeds as the output of the LSTOutputConverter.
• The option to (not) include T5s in the CMSSW TrackCandidate coming out of the LSTOutputConverter.
• Disentangles the LST reconstruction from validation modules.
• Synchronizes with the latest standalone master branch developments (SegmentLinking/TrackLooper@b5dfd9d9f97c882ac64ee1a1a52d1159114ce979) and simplifies the pixelSeed input logic by dropping the iteration algo information.

The PR has been tested by running the CMSSW configuration on a few events and verifying that the TrackCandidates are the same and that the TrajectorySeed variables make sense (are reasonably close to those of the corresponding TrackCandidates).

Coupled with SegmentLinking/TrackLooper#280.

[VourMa]

scram b -j 12 code-checks >& c.log

When running this, the output file includes a few lines like this:

1190 warnings generated.
Suppressed 1190 warnings (1189 in non-user code, 1 with check filters).
Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.

Is this an issue? In 45cf6f9 I applied all of the changes applied automatically to our code.

[slava77]

When running this, the output file includes a few lines like this:

I don't think I ever payed attention to the log files as long as the command returned successfully.

[VourMa]

I don't think I ever payed attention to the log files as long as the command returned successfully.

The command returned successfully and everything was updated accordingly, so I think this is ready to be merged.