Extraneous Warnings on clean import

[lowlydba]

Before submitting the bug

• Ensure you are able to reproduce it on the latest released version (we release often)
• Verified this bug is not already reported in an issue
• Verified errors are not related to permissions
• Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Describe the bug
I'm not sure how common of a scenario this is, but I ran into it while troubleshooting #159.

When doing an import without a PSDrive setup, but with a JSON file set through Set-DcnConfiguration, when dbaclone.psm1 imports the public function scripts, it results in two of them issuing warnings related to the PSDrive. These occur before the creation of the PSDrive in postimport.ps1, so will always be thrown in this case.

dbaclone/functions/clone/Get-DcnClone.ps1

Lines 153 to 161 in 1386e86

	elseif ($informationStore -eq 'File') {
	# Create the PS Drive and get the results
	try {
	if (Test-Path -Path "DCNJSONFolder:\") {
	# Get the clones
	$results = Get-ChildItem -Path "DCNJSONFolder:\" -Filter "*clones.json" | ForEach-Object { Get-Content $_.FullName | ConvertFrom-Json }
	}
	else {
	Stop-PSFFunction -Message "Could not reach clone information location 'DCNJSONFolder:\'" -ErrorRecord $_ -Target "DCNJSONFolder:\"

and

dbaclone/functions/image/Get-DcnImage.ps1

Lines 142 to 149 in 1386e86

	elseif ($informationStore -eq 'File') {
	try {
	if (Test-Path -Path "DCNJSONFolder:\") {
	# Get the clones
	$results = Get-ChildItem -Path "DCNJSONFolder:\" -Filter "*images.json" | ForEach-Object { Get-Content $_.FullName | ConvertFrom-Json }
	}
	else {
	Stop-PSFFunction -Message "Could not reach image information location 'DCNJSONFolder:\'" -ErrorRecord $_ -Target "DCNJSONFolder:\"

To Reproduce
Steps to reproduce the behavior:

Import-Module dbaclone
Set-DcnConfiguration -InformationStore File -Path "C:\"

Remove-Module dbaclone -Force
# Simulate it was removed, never created, or encountered an error when creating...
Remove-PSDrive "DCNJSONFolder"

Import-Module dbaclone

Expected behavior
Ideally loading these functions during import shouldn't run them in a way that attempts to read from the PSDrive, in the case where it doesn't exist for some reason.

Screenshots
I added a few debug warnings to illustrate:

Environmental data

Name                           Value
----                           -----
PSVersion                      5.1.14393.4583
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.4583
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1