CLI: Find PRO packages more accurate

[berkansasmaz]

Related place:

abp/framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/Version/CommercialPackages.cs

Line 15 in 6da923a

public static bool IsCommercial(string packageId)

Reason:

abp/framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/Version/PackageVersionCheckerService.cs

Lines 105 to 126 in b037fcf

	public async Task<List<string>> GetPackageVersionListAsync(string packageId, bool includeNightly = false)
	{
	if (includeNightly)
	{
	return await GetPackageVersionsFromMyGet(packageId);
	}
	if (CommercialPackages.IsCommercial(packageId))
	{
	return await GetPackageVersionsFromAbpCommercialNuGetAsync(packageId);
	}
	else
	{
	var packagesFromNugetOrg = await GetPackageVersionsFromNuGetOrgAsync(packageId);
	if (packagesFromNugetOrg != null)
	{
	return packagesFromNugetOrg;
	}
	}
	return await GetPackageVersionsFromAbpCommercialNuGetAsync(packageId);
	}

It first looks at nuget.org and then nuget.abp.io for commercial packages in the current structure. This causes performance issues.

In addition, it creates the perception that there is an error in the users.
Because when you can't find it on nuget.org, users will see an error like the one below:

HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.account.pro.admin.blazor.server/index.json with an error: 404-Not Found.

Related QA question: https://support.abp.io/QA/Questions/4756#answer-3a0a227c-488f-e4c5-29c3-5b8f1d686b84