Align the Archive_AutoArchiveSize and Minimum Archive Size to be based on Tag Count, not Record Number Count

Schedule data archive shifts occur and create archive files based upon a Minimum Archive Size calculation. This calculation is based upon the total count of record numbers. When large amounts of tags are deleted, the total number of tags is reduced but the record number count remains the same...thus creating a huge discrepancy between the two counts. The minimum archive file size is based on total record numbers. Thus, if you delete a large number of tags (e.g. Reduce a 5M tags system down to 1M tags after splitting a collective into multiple collectives)....then the system will artificially create very large archive file sizes which are filled at a low percentage. This calculation result is different from the Archive_AutoArchiveSize calculation which looks at the count of active tags. The deviation between the two leads to confusion and difficulty properly scheduling archive shifts, along with generating incorrect % full results (which look at the total record number count, not the total tags....this would be artificially false low).