Nugetization refactor of DataApiBuilder

[rohkhann]

Why make this change?

This change is being made to allow nugetization of generic IP of Data api builder so that it can be consumed as a nuget by separate projects. There is no logic change or user experience change in this pr. It is a refactor of all the IP classes used by dab components into a separate c# library. Change has been internally discussed with DAB team as part of nugetization effort for DAB IP. This is an initial draft pr.

What is this change?

Created a new c# class library project that references auth and config projects. Moved all the folders from Service project to the new c# class project.

Pr is split into three commits for easier review:

1. In commit 1, I just copied over the files into Microsoft.AzureDataApiBuilderSDK from the Service project and added appropriate references to the auth and config projects. Also did the renaming of the namespaces
2. In commit 2, I changed the references of all existing code to use the appropriate helpers from this SDK rather than the same folders on the Service project.
3. In commit 3, I deleted the folders from the service project.

Folders moved out of service to new project Azure.DataApiBuilder.Core:

1. AuthenticationHelpers
2. Authorization
3. Configurations
4. Models
5. Parsers
6. Resolvers
7. Services

New file created: Utils.cs in Core.

Service Old Folder Structure:

Service project New Folder Structure:

How was this tested?

• Integration Tests
  Ran data api builder locally against mssql db
• Unit Tests
  Ran unit tests listed on the contributions guidelines page

Sample Request(s)

• Example REST and/or GraphQL request to demonstrate modifications
  No logic or workflow changes, just moving of files to a seperate project and reference changes
• Example of CLI usage to demonstrate modifications
  No logic or workflow changes, just moving of files to a seperate project and reference changes

[mbhaskar]

Thank you for the changes. Could you also probably add basic design/block diagram of the proposed structure and how it is used? If you already have it in any other design doc, please link it here

[aaronpowell]

Some tidy ups proposed.

[Aniruddh25]

Overall looks good, left few rename suggestions.

[aaronpowell]

Really minor nit (can be ignored), otherwise good once tests pass.

[seantleonard]

Looks good, one nit about now-unneeded code