feat: Add GetDomainsForUser API

[sagilio]

Fixes: #147

Can not update DynamicExpresso.Core to v2.5.0: dynamicexpresso/DynamicExpresso#144

[hsluoyz]

@thoraj plz review.

[thoraj]

@thoraj plz review.

I will be happy to review. Is there a nuget feed where I can pick up the build?

[hsluoyz]

@sagilio is there a nightly nuget feed for this PR, which can be used for testing?

[sagilio]

@hsluoyz Secrets are not passed to workflows that are triggered by a pull request from a fork. Pushing myget packages needs the MYGET_TOKEN.

[sagilio]

@thoraj plz review.

I will be happy to review. Is there a nuget feed where I can pick up the build?

I have changed the CI. We can merge first, It will release on MyGet feed.
You can use this version to test

[sagilio]

@hsluoyz Secrets are not passed to workflows that are triggered by a pull request from a fork. Pushing myget packages needs the MYGET_TOKEN.

@hsluoyz So, I try to split the build and release workflow to build and release (use event trigger here) and they still use the semantic release.
I think It will make the release more flexible. e.g.: Sometimes we need more than one PR to release a new version.

[hsluoyz]

@sagilio I didn't see a new release coming after this PR merge. We still should do this:

Let's say the latest version is v1.2.2. When we have new PR:

1. Make nightly release to MyGet for each new PR update, using v1.2.2-1, v1.2.2-2, etc.
2. Make semantic-release to NuGet after PR merge using v1.2.3.

[sagilio]

@hsluoyz We can not release to MyGet from fork repo.

Now, the release policy like this. it only added one more confirmation after merge:

1. Make nightly release to MyGet after PR merge (We also can view the semantic release dry-run result now).
2. Make semantic release to NuGet after manually trigger the release workflow.

I think this is a better way for this repo. In fact, it more like the build pipeline and release pipeline in Azure DevOps.
I have triggered a release just now and the v1.8.0 version is released, https://github.com/casbin/Casbin.NET/actions/runs/867798888.

[hsluoyz]

@sagilio how to trigger semantic release for me?

[sagilio]

@hsluoyz https://github.com/casbin/Casbin.NET/actions/workflows/release.yml

[thoraj]

I noticed there was a new package v1.8.0 on nuget so I ran some test on that. I got the expected results so LGTM.

I only tested providing a user parameter like this.

domains = enforcer.GetDomainsForUser("@user1");

I did not provide anything for the roleType, as I'm not sure what to expect for these cases.

[sagilio]

@thoraj It will use the default role type.

Casbin.NET/NetCasbin/Model/PermConstants.cs

Line 14 in e5df0b3

public const string DefaultRoleType = "g";