Kiota Dotnet Mono repo migration

[andrueastman]

Fixes #238

In Summary changes include

• Restructure csproj file to be simpler to eliminate repeated configs (which are now held in Directory.Build.props)
• Update version stratey to be common accross libs (pulled from Directory.Build.props)
• Updates CI and release pipelines/scripts
• Moves sources of other libraries to be held in one project solution (Microsoft.Kiota) as below

 └─Microsoft.Kiota.sln
 └─src
    └─abstractions
    └─authentication
       └─azure
    └─http
       └─httpClient
    └─serialization
       └─json
       └─form
       └─text
       └─multipart
 └─tests
    └─abstractions
    └─authentication
       └─azure
    └─http
       └─httpClient
    └─serialization
       └─json
       └─form
       └─text
       └─multipart

CI/Validation

• Release pipeline artifacts can be inpected at the run at - https://microsoftgraph.visualstudio.com/Graph%20Developer%20Experiences/_build/results?buildId=155464&view=results
• PR validation at https://github.com/microsoft/kiota-abstractions-dotnet/actions/runs/9837309232/job/27154841826?pr=262

Notes
To separate concerns, sources are migrated as is. Resolving any issues with the source would ideally be done separately.

[baywet]

This is good progress, I left a couple of comments to help. Also:

• dependabot configuration needs to be updated.
• repo url in csproj needs to be changed to kiota-dotnet (I'll rename the repo after we merge)

[andrueastman]

@baywet With regards to the dependabot configs, I notice the config is already set to scan the repository root(this should pick up any csproj files). Any chance you had different thoughts here with regards to updating this?

[andrueastman]

note: The preview suffix is intentional for now to double check the release process end to end without breaking with a production version with regards to sourcelink, signing and all packages getting published. Will empty the value in a separate PR once previews are confirmed to be valid.
Run here already validates proper signing but best to be sure.

[sonarcloud]

Quality Gate failed

Failed conditions
2 Security Hotspots
70.5% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint