Config validation and new developer settings, local tracing, performance optimization

feat: resolve #394: Implement the standardized Development Configuration Options.
feat: resolve #395: Implement IRollbarConfig's Transmit option.
feat: resolve #396: Implement RethrowExceptionsAfterReporting IRollbarConfig option.
feat: resolve #397: Implement local SDK logging via TraceSource and supporting verbosity control.
feat: resolve #398: Implement dedicated local logging of payloads coming through the RollbarLogger.
perf: resolve #383: Make sure loggers do not queue new payloads during rate-limit suspension.
feat: resolve #378: Implement config validation on every logger re/configuration.
refactor: resolve #393: Eliminate all current build warnings.
test: resolve #401: Fix failing CI unit tests (on some of the build targets)

v3.1.0 - Server guided reporting rate limits, config validation, internal errors aggregation and more

• resolve #379: Add Validate() method to IRollbarConfig.
• resolve #368: Make SDK to obey service-side enforced rate limits unless client-side RollbarConfig defines one
• resolve #384: Make sure relevant queues are flushed on rate-limit suspension
• resolve #370: Consider aggregation of errors during blocking logging and attaching them to the TimeoutException.
• ref #366: Better information regarding using Person object without ID.
• resolve #380: Misconfigured payloads can be dequeued much sooner.
• resolve #388: Remove ValidateIt() from DtoBase type and replace its overrides based on IValidatable
• resolve #389: Fix failing unit-tests (after recent PR merges)
• resolve #381: Correct unit tests that are failing on the CI server.

Improvements

• resolve #375: Scrub fields don't appear to be scrubbed within request body's JSON data
• code cleanup, typo corrections, etc.

• resolve #373: Rollbar.PlugIns.Log4net - Make IRollbarConfig API publicly available to the plug-in users

Fixes and improvements

• resolve #355: AddRollbar() is missing in release 3.0.3
• resolve #367: Extra fail-safe guards when processing faulty payload bundles within the queues
• resolve #369: Change default rate limit to 5K per minute
• ref #352: Increase Core's unit test coverage around recovery from invalid payloads and failures

Fixes and Improvements

• resolve #352: Create automated release build script
• resolve #340: Add v3 specifics info into "Blocking vs Non-Blocking Use" section of ReadMe.md.
• resolve #341: "Merge" v3 release notes content into Rollbar.NET docs on Rollbar.com.
• resolve #343: Fix latest Codacy issues.
• resolve #348: Rollbar.NetCore.AspNet.RollbarLogger: payload title changes
• resolve #349: Rollbar.RollbarLogger: improve granularity of internal error reporting during main phases of payload bundle handling.
• resolve #295: Improve granularity of internal error reporting when Json serialization of a payload fails.
• resolve #293: Please allow AppSettingsUtility to work for projects targeting .net full framework.
• resolve #278: Create unit tests for ExceptionUtility

v3.0.2 Rollbar.NET Notifier SDK Release Notes

Upgrade Notes

Depending on how you were integrating the Notifier into your application prior to v3, you might have to perform some or all of the following changes when moving to v3 of our SDK:

• in addition to Rollbar assembly reference, add references to relevant .NET Specific Technology/Application Integration Modules (these modules are described in the next sections);
• if you did have to add one or more references to the .NET Specific Technology/Application Integration Modules, you will have to update namespaces of the types that were moved from Rollbar to these new modules;
• if you have any calls to IAsyncLogger's methods where you are waiting on the returned Task object to complete, you will now have to wrap your data (originally passed into the logging method) into
  an ObjectPackage instance while setting its MustApplySynchronously flag and pass the wrapper instead of the original data into the same logging method.

All of these changes are very straightforward and the compiler will help you and guide you along the way as needed.
Most of it is just a "find-and-replace" with a few "compile-and-correct-the-build-issues".

General SDK-wide Notes

Overview

Starting with v3 we split the Rollbar.NET Notifier SDK into more components or modules.

These components can be logically grouped into the following categories:

• Core Modules
• .NET Specific Technology/Application Integration Modules
• Third-party Logging Libraries/Frameworks' Integration Plug-ins

Core Modules implement the very basic stand-alone core functionality of the Rollbar.NET Notifier.
They have least possible amount of dependencies and only rely on functionality provided by most basic .NET implementation types
that are common across all of the supported .NET Standard implementations. So, if you only care about using core SDK concepts like:
IRollbar, ILogger, IRollbarConfig, RollbarFactory, RollbarLocator,IRollbarPackage, Rollbar.DTOs, RollbarQueueController, ITelemetryCollector, ITelemetryConfig, some basic Rollbar utility classes
and you are planning to implement all the integration of these classes into your application on your own - use the Core Modules only.

If you care about functionality that we implemented to simplify integration of the Notifier core functionality into a specific .NET application technology/framework, like
.NET Framework ASP.NET or .NET Core ASP.NET etc. - you may want to pull in some of the .NET Specific Technology/Application Integration Modules.

If you want to have the Notifier integrated as a simple plug-in expected by a commonly used third-party logging library/framework,
like Serilog, log4net, etc. (because you are already relying on one of these) - look for proper plug-in among the Third-party Logging Libraries/Frameworks' Integration Plug-ins.

Here are examples of currently available modules in each category:

• Core Modules:

  1. Rollbar.

• .NET Specific Technology/Application Integration Modules:

  1. Rollbar.Net.AspNet,
  2. Rollbar.Net.AspNet.Mvc,
  3. Rollbar.Net.AspNet.WebApi,
  4. Rollbar.NetCore.AspNet.

• Third-party Logging Libraries/Frameworks' Integration Plug-ins:

  1. Rollbar.PlugIns.Log4net,
  2. Rollbar.PlugIns.MSEnterpriseLibrary,
  3. Rollbar.PlugIns.NLog,
  4. Rollbar.PlugIns.Serilog.

Each of the modules is available via NuGet as stand-alone package.

We are also unifying versioning all of the modules to follow common SDK versioning.

Fixes and Improvements

v3.0.0-preview

• resolve #287: Add more seamless integration with ASP.NET (Full Framework) based applications.
• resolve #288: Add sample of Rollbar.NET within ASP.NET (Full Framework) based applications.
• resolve #289: Improve flexibility composing Data DTO.
• resolve #290: Improve comments related to meaning of DTOs properties.
• resolve #291: Define IRollbarPackage
• resolve #296: Out of memory exception with high exceptions rate in multi threaded environment.
• resolve #297: Assumption failure when setting nullable value for a key in ExtendableDtoBase
• resolve #298: Make initialization of RollbarConfig via config files or explicitly specified access token as mutually exclusive.
• resolve #300: Implement packaging strategy abstraction.
• resolve #301: Implement packaging strategy decorator abstraction.
• resolve #316: Implement packaging strategy for arbitrary object payload.
• resolve #302: Implement packaging strategy for messages.
• resolve #303: Implement packaging strategy for exceptions.
• resolve #304: Implement packaging strategy for ExceptionContext.
• resolve #312: Implement packaging strategy for Data DTO
• resolve #313: Implement packaging strategy for Body DTO
• resolve #305: Implement packaging strategy decorator for Person info.
• resolve #314: Implement packaging strategy decorator for custom Key Value Pairs
• resolve #315: Implement packaging strategy decorator for custom RollbarConfig
• resolve #306: Implement packaging strategy decorator for HttpRequest info.
• resolve #307: Implement packaging strategy decorator for HttpContext info.
• resolve #311: Rename packaging strategies and their decorators into "Package"s and "PackageDecorator"s
• resolve #310: Implement PayloadBundle
• resolve #308: Implement automatic strategy/Data time-stamping.
• resolve #309: Complete integration of packaging strategies
• resolve #317: Consolidate dependencies versions.

v3.0.1-preview

• resolve #322: General codebase cleanup.
• resolve #321: Address latest Codacy review results.
• resolve #320: Update CI build scripts/environment.
• resolve #325: Extract integration with .NET Framework ASP.NET MVC into separate project (Rollbar.Net.AspNet.Mvc).
• resolve #326: Extract integration with .NET Framework ASP.NET Web API into separate project (Rollbar.Net.AspNet.WebApi).

v3.0.2

• resolve #322: General codebase cleanup.
• resolve #321: Address latest Codacy review results.
• resolve #320: Update CI build scripts/environment.
• resolve #325: Extract integration with .NET Framework ASP.NET MVC into a separate module/Nuget-package Rollbar.Net.AspNet.Mvc.
• resolve #326: Extract integration with .NET Framework ASP.NET Web API into a separate module/Nuget-package Rollbar.Net.AspNet.WebApi.
• resolve #327: Extract integration with .NET Core ASP.NET (middleware) into a separate module/Nuget-package Rollbar.NetCore.AspNet.
• resolve #332: Complete cleanup of the Request DTO constructors that are based on specialized framework types
• resolve #330: Implement RollbarHttpModule as part of Rollbar.Net.AspNet integration module/Nuget-package.
• resolve #334: Fix Azure build pipeline
• resolve #329: ASP.NET code middleware not reporting request data.
• resolve #331: Verify and correct sample apps to adopt latest SDK changes related to multiple integration modules
• resolve #336: Extract SdkCommon.csproj and clean-up SDK projects' settings
• resolve #337: Unify/sync-up SDK components versioning
• resolve #318: Add explicit build target for .NET Core 2.2
• resolve #338: Fix all the build warnings across the SDK
• resolve #263: PostBody is always null
• resolve #335: Update documentation regarding v3 changes

Notes per SDK Module/Nuget-Package

Core Modules

The most fundamental API of the Notifier is ILogger. It defines a collection of convenience methods for sending different kinds of data payloads using different logging levels flags.
Internally, any implementation of the ILogger that we have performs these three distinct steps when any of its logging methods is called:

1. enqueue the data object(s) to log for future transmission to the Rollbar API;
2. package/snap-shot the incoming/enqueued data object(s) into proper Rollbar data structure while applying some rules specified as part of relevant RollbarConfig instance;
3. transmit the enqueued items to the Rollbar API according to relevant RollbarConfig settings.

To minimize impact of logging on the calling thread, ideally, it would be nice to perform all the steps on auxiliary background thread(s).

However, in cases when highly mutable data is about to be logged it is essential to have step 2 performed on the calling thread before returning from the logging method.
In v2 we introduced IAsynLogger to help handle such cases. Its methods were a complete copy of ILogger's methods with one main difference - they all used to return a Task,
so that the client code could wait for it to complete steps 1 and 2 before proceeding further if that is what needed in a specific case.
While it was a nice flexible and easy to use solution from API point of view, the tasks did not perform well (as we learned it the hard way) under EXTREMELY high AND sustained rate of load.
So, in v3, we went away from the Tasks and removed IAsynLogger all together. We are now back to having only ILogger and we have a substitute for the eliminated Tasks in the form of IRollbarPackage.
Think of the IRollbarPackage as a basis for implementing arbitrary data packaging strategies with explicit flag (named as MustApplySynchronously) that signifies need to apply the packaging (steps 1 and 2)
on the calling thread before returning from a logging method. We also provide with abstract base classes like RollbarPackageBase and RollbarPackageDecoratorBase for implementing custom packaging strategies and their decorators.
We used these abstraction to implement our own collection of packagers and their decorators. All of them are available to the SDK users as well.
In addition to helping us in getting away from the Tasks usage, these new abstractions allow for very flexible and powerful ways to bundle a lot specific types of data into a single ...

What's new and what are the most significant changes of v3 of the SDK?

  Rollbar Notifier/Logger performs 3 distinct internal operations when forwarding any data to the Rollbar API:
    1. queuing the data object(s) to log into a queue associated with particular Rollbar access token;
    2. packaging/parsing the data object into a Rollbar API specified data format;
    3. transmitting the packaged data from a queue to the Rollbar API.
  
  When you call any of the ILogger's logging methods on a RollbarLogger instance, the operation 1 is executed and the method returns immediately, 
  while operations 2 and 3 are performed later on asynchronously on a background thread.
  
  When you call any of the ILogger's logging methods via AsBlockingLogger(timeout) ILoger's instance - all the three operations performed on 
  the calling thread (unless timeout with a timeout exception) before the method returns.
  
  If you prefer operations 1 and 2 (packaging and queuing) to be performed synchronously on the logging method calling thread before a logging method 
  returns - call a logging method of ILogger directly on a RollbarLogger instance (not the one returned by AsBlockingLogger(timeout)) but wrap the logged
  object into an ObjectPackage (implementing the IRollbarPackage interface) while setting its constructor optional parameter/flag mustApplySynchronously to true.
  
  The approaches described above allowed us to remove IAsyncLogger interface from the SDK (and, most importantly, stop using its Task return types that may be
  a cause of some resource contention when used within application hosts that are heavily multi-threaded with very active threads and use of logging that are 
  operating above some threshold defined by the host hardware and the rest of execution environment).
  
  The SDK also includes rich collection of other types implementing the IRollbarPackage interface in form of either ...Package(s) or ...PackageDecorator.
  The decorators are the packages and can be "wrapped" around any other package instance. These packages are used to define any arbitrary data packaging rues and
  at what point of the logging pipeline to apply them. Most inner wrapper is executed first, most outer - last.

Improvements and fixes:

  - resolve #287: Add more seamless integration with ASP.NET (Full Framework) based applications.
  - resolve #288: Add sample of Rollbar.NET within ASP.NET (Full Framework) based applications.
  - resolve #289: Improve flexibility composing Data DTO.
  - resolve #290: Improve comments related to meaning of DTOs properties.
  - resolve #291: Define IRollbarPackage
  - resolve #296: Out of memory exception with high exceptions rate in multi threaded environment.
  - resolve #297: Assumption failure when setting nullable value for a key in ExtendableDtoBase
  - resolve #298: Make initialization of RollbarConfig via config files or explicitly specified access token as mutually exclusive.
  - resolve #300: Implement packaging strategy abstraction.
  - resolve #301: Implement packaging strategy decorator abstraction.
  - resolve #316: Implement packaging strategy for arbitrary object payload.
  - resolve #302: Implement packaging strategy for messages.
  - resolve #303: Implement packaging strategy for exceptions.
  - resolve #304: Implement packaging strategy for ExceptionContext.
  - resolve #312: Implement packaging strategy for Data DTO
  - resolve #313: Implement packaging strategy for Body DTO
  - resolve #305: Implement packaging strategy decorator for Person info.
  - resolve #314: Implement packaging strategy decorator for custom Key Value Pairs
  - resolve #315: Implement packaging strategy decorator for custom RollbarConfig
  - resolve #306: Implement packaging strategy decorator for HttpRequest info.
  - resolve #307: Implement packaging strategy decorator for HttpContext info.
  - resolve #311: Rename packaging strategies and their decorators into "Package"s and "PackageDecorator"s
  - resolve #310: Implement PayloadBundle
  - resolve #308: Implement automatic strategy/Data time-stamping.
  - resolve #309: Complete integration of packaging strategies
  - resolve #317: Consolidate dependencies versions.

Hot-fix:
- resolve #296: Out of memory exception with high exceptions rate in multi threaded environment.