SPM-1750: Ability to identify Flexlink Contracts in NCompBase

NCompBase team to check how Flexlink accounts are identified in Base today. The goal is to find out if there is a better way to identify these accounts besides maintaining a cross reference table, so that same logic can be utilized for any custom account specific requirements.

Background from MI request:

Currently we are unable to request id card for flexlink contracts because we pass alpha prefix separate from contract number. We need to fix the process for id card submission similar to how we have it for inquire claim details. If the contact is flexlink, we need to pass alphaprefix and contract number combined.  We have 4 delegated tables for flexlink for this purpose, Flexlink Table for Generic Use, Flexlink Table for Manage Claims, Flexlink Table for View Totals, and Flexlink Table for View Benefits.

Please find attached CS xmls for following patterns. 

->Contract element having 9 digit enrollee Id along with prefix (No Issue)

->Contract with 9 digit enrollee id and prefix separate like regular contract. (Fails)

Requirement 1. If Contract is flexlink pass combined alphaprefix and contract.

Requirement 2. Retire Flexlink Table for View Benefits as we no longer use it. Currently it is set to return false always.

Requirement 3. Retire Flexlink Table for View Totals and use Flexlink Table for Generic Use instead. 

Requirement 4. Flexlink Table for Generic Use would be the table to use for view totals and id card to identify if a group is flexlink or not and follow flexlink logic.