Update PI-AF install procedure to handle custom PIFD Naming

If hosting multiple AF DBs on a single SQL instance it is necessary to rename the PIFD default name to a unique name. For instance PIFD_<AFHostname>

The current PI-AF install routine does not handle this situation - forcing a step to rename the target DB back to 'PIFD', complete install on new host, rename 'PIFD' back to intended custom name and reconfig of the AF Service Config file for connection string.

This process could be improved by including a check/allow specification of the actual AF DB name during installation process. We encounter this staging replacement servers on workload move off old hardware.