cptResourceDemand - allow export of full baseline

[AronGahagan]

Request:

Optionally allow export of Full Baseline in Resource Demand.

Todo:

• assign this issue
• assign issue type (Bug, Feature, Task)
• label the issue with codemodule (so fixes can be aggregated and hotfixed together)
• checkout appropriate branch and create topic branch
• design, code and test
• update codemodule <cpt_version>x.y.z</cpt_version>
• update CurrentVersions.xml manually
• commit message should begin with Issue #XXX -
• commit the change(s)
• merge topic into appropriate branch(es) and push
• delete topic branch

[AronGahagan]

This is going to render the dataset extremely large.

1. Export to CSV by day and mapped to fiscal periods.
2. Summarize and group the output by Week? Month?
3. Don't overload the excel file with data!

[AronGahagan]

If FiscalPeriods is selected then we don't need to do anything with DAY,WEEK,FTE_WEEK,FTE_BL_WEEK in the final export. We slot the days into fiscal periods via SQL query and group / summarize before dumping into the report.
And perhaps take a note from COBRA and use a "CLASS" field (BCWS,ETC) then we only need HOURS,[COST_A],PERIOD,FTE.

[AronGahagan]

ADODB and SQL is a huge mistake if external joins are necessary.
Built a KEY of the GROUPBY fields, and a VALUE of the WORK/COST.
Export is faster.
Also automatically grabbed the activeproject.calendar exceptions for the HOLIDAYS thing.
Export Full Baseline feature is working. Need to incorporate the multiple rate sets.
DataSource structure changed to use CLASS for BCWS/ETC, RATE_TABLE, And ACTIVE_RATE_TABLE(bool) to allow for better filtering.
Many performance improvements.