CSM update didn't check prereq level of ibm-flightlog

[thanh-lam]

Describe the bug
When updating CSM to 1.6.0 using yum, it didn't check compatibility level of existing ibm-flightlog-*. A back level of ibm-flightlog was without notice. The admin or users may not be aware that they are running with in-compatible level of ibm-flightlog.

To Reproduce
Steps to reproduce the behavior:

1. With an existing level of CSM, for example 1.5.3, run yum update ibm-csm-core-<new level>*
2. See that the update completed successfully.
3. Check for level of ibm-csm: rpm -qa | grep csm
4. Check for level of ibm-flightlog: rpm -qa | grep flightlog
5. Update ibm-flightlog: yum update ibm-flightlog-<new level>*

Expected behavior
The update (yum or rpm) should fail or display a WARNING message about old ibm-flightlog level.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Machine [IST alt cluster]
• Version [CSM 1.6.0]

Additional context
rpm requirement does not show level of ibm-flightlog-*. One may assume that CSM would work with any level of ibm-flightlog. That would be a risky assumption.

# rpm -qR ibm-csm-core-1.6.0-2337*
...
libc.so.6()(64bit)
libc.so.6(GLIBC_2.17)(64bit)
libdl.so.2()(64bit)
libdl.so.2(GLIBC_2.17)(64bit)
libflightlog.so()(64bit)
...

Issue Source:
A new level of ibm-flightlog is always built with a new level of CSM. Therefore, the new ibm-flightlog should be updated by yum.