CFLGraphBuilder can be useful to both CFLSteensAliasAnalysis and CFLAndersAliasAnalysis, just like CFLGraph. Move it out to for future use by CFLAndersAliasAnalysis.
Since CFLGraphBuilder needs to use CFLSteens/CFLAnders for interprocedural analysis, I've made it template on the type of AA that uses it. This does impose an implicit API constraint on the AA: we expect it to a getAliasSummary() member function so that the summary of any functions can be retrieved. I didn't make any attempts to properly enforce this constraint (except mentioning it in the documentation), since doing that may require some SFINAE tricks that'll confuse the main point of the codes. Concept will help on that, but we are still not there :)