Add SurrealDB hosting/client integration

[Odonno]

Closes #<ISSUE_NUMBER>

Project Additions and Updates

• Added new SurrealDB projects to the solution, including Aspire.CommunityToolkit.Hosting.SurrealDb, Aspire.CommunityToolkit.SurrealDb, and their respective test and example projects

Dependency Updates

• Added new dependencies:
  • SurrealDb.Net as a dependency of the SurrealDB client integration
  • Bogus to generate fake data, to be used for testing purposes
  • SurrealDb.MinimalApis.Extensions to provide extension methods for Minimal APIs. Used to create API endpoints for the example API service project with the minimum of code.

Code Ownership

• Updated the CODEOWNERS file to include new SurrealDB projects and assigned ownership to @Odonno

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • Docs are written
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Contains NO breaking changes
• Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

Unable to run tests that RequiresDocker as of now. For some reasons, the containers are never created. Maybe this is the reason. I am using Rancher Desktop. For info, those tests worked in the previous PR I mentioned.

[Alirexaa]

@Odonno thanks for the contribution. For runnig CI Actions, Please fix the confilict with the main brach.

[aaronpowell]

A good start and I can see how it'll fit into the Toolkit overall. As @Alirexaa mentioned, there's some merge conflicts that will block running a CI job on this.

I've left some comments/changes throughout the PR too.

[aaronpowell]

For the CODEOWNERS to be valid you would need to join the maintainer group - is that something you're interested in (I'm guessing so since you put yourself down as the owner 😉)

[Odonno]

Why not.

[Odonno]

That should be good now. Can you reopen the PR @aaronpowell ?

[Odonno]

@aaronpowell ?

[Odonno]

@aaronpowell Are you there?

[aaronpowell]

I'm unable to reopen the PR, looks like the branch has had a force push done since it was closed so the PR isn't able to reopen

[Odonno]

Ok, I opened a new PR #365

[aaronpowell]

I'm cautious on the maintainability of these tests, as we've had some problems in the past with this style in addition to the ones that use the examples app host project.

Once we're able to run CI on them, let's evaluate properly, but also consider what these tests are testing that the functionality the Community Toolkit provides vs what is .NET Aspire. For example, if the volume persistence fails, is that a Toolkit bug or Aspire bug? Assuming all our tests cover setting the right annotations isn't the Toolkit doing the right stuff?

[Odonno]

I can't really tell. But at least it can confirm that the database integration works as expected for those scenarii.

[aaronpowell]

Let's get some tests in here that assert all the right annotations are setup across the container, the mounts, args, etc.

[Odonno]

Do you have an example? I suppose Verify would be useful for this kind of tests?