backport: use GitHub actions (linux support) (#236)

[v1v]

Backport #236

[Mpdreamz]

https://github.com/elastic/ecs-dotnet/actions/runs/4064290493/jobs/6997544409 this seems odd it should not publish prereleases like this to nuget Unless its building from a tag.

[Mpdreamz]

https://github.com/elastic/ecs-dotnet/releases/tag/1.6.0-alpha1.50 should have not been created.

[v1v]

https://github.com/elastic/ecs-dotnet/actions/runs/4064290493/jobs/6997544409 this seems odd it should not publish prereleases like this to nuget Unless its building from a tag.

https://github.com/elastic/ecs-dotnet/actions/runs/4064290493/workflow#L5 even the build should have not been triggered

The reason seems to be

c9d84f2

I wonder whether the on: create is not correct, let me double check

[v1v]

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#create

Runs your workflow when someone creates a Git reference (Git branch or tag) in the workflow's repository.

And it seems the filter is not honoured as per actions/runner#1007 (comment)

[v1v]

https://github.com/elastic/ecs-dotnet/releases/tag/1.6.0-alpha1.50 should have not been created.

What do we do?

[Mpdreamz]

I deleted the tag/release. Since the actual publish to nuget failed there is not other cleanup needed.

We might need to generate a new key to be able to publish again.

[v1v]

We might need to generate a new key to be able to publish again.

I might need to find how to do it, do you happen to remember how?