Pelican plugin stage sometimes gets new classads, sometimes old

[joereuss12]

Pelican Version:
Run ./pelican --version to get version number.

Pelican Service:

• Client
• Plugin

Jason overheard a discussion I was having with Cole about how plugin staging was getting classads with a "\n" separating them but the plugin itself gets them separated by ";". Jason mentioned that it depends whatever version of classads are passed to the plugin/hook since one version separates by "\n" and another separates by ";". This should be something we check for when parsing classads to ensure Pelican works with both versions of them.

This requires a little more investigation as well.

[joereuss12]

This prompts more investigation so I am going to keep this an issue but since I have not had many problems in this area, I'm going to remove the milestone because I am not sure when I will be looking into this more.