fix: correctly reading bufferRetainedInvalidPayloads from appsettings

[DinoSourcesRex]

What issue does this PR address?
bufferRetainedInvalidPayloadsLimitBytes is not read from appsettings

Does this PR introduce a breaking change?
No, I hope not

Please check if the PR fulfills these requirements

• The commit follows our guidelines
• Unit Tests for the changes have been added (for bug fixes / features)

Other information:
I have not created an issue for this as it is only a small change. If you'd like me to do so before the merge I can do it.

I discovered this when trying to figure out why invalid-guid files were not being removed from my log folder.

[DinoSourcesRex]

Looks to me like the myget index, dotnet-core in the nuget.config is not pointing to an actual resource anymore. Not entirely sure, some resources online point to adding a proxy into the nuget.config package.

If no one knows what is going on I can try to fix this at some point, not sure if I have the appropriate permissions or not though.

[DinoSourcesRex]

Well. According to this link dotnet.myget.org was retired (answer from a microsoft employee).

[mivano]

I will need to look into that. Thanks for the PR. Will get back to you. Op ma 11 okt. 2021 om 07:46 schreef Dino ***@***.***>

…

Well. According to this <https://docs.microsoft.com/en-us/answers/questions/337663/invalid-certificate-for-mygetorg.html> link dotnet.myget.org was retired (answer from a microsoft employee). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#398 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFDG57UTXQWNBXLHYPPSI3UGJ23ZANCNFSM5FV2PZDA> .

[DinoSourcesRex]

@mivano just FYI looks like I duplicated this PR - that's what I get for not checking existing PRs.