Creating a new project for building a strongly named version

[bothzoli]

With this PR a new project libc.eventbus.strongname was created.
This project references the source files from libc.eventbus but when built will also sign the created DLLs.
This allows the libc.eventbus.strongname nuget package to be used where a strongly named assembly is required.

The common project properties are moved to the Common.Build.props file.
Solution files were added to the solution.
The duplicate REAMDE.md file was removed.
A signing key was added to the solution.
A minor version bump was applied (since there are no code changes).

Resolves: #10

[sfmohassel]

Thanks man

[sfmohassel]

Dear @bothzoli,
Please also include your name as authors :)

[bothzoli]

Thank you very much, I really appreciate this 😊

[sfmohassel]

Nice hack!

[bothzoli]

Yeah, I thought, there must be a better way of doing this other than duplicating the README file :)

[sfmohassel]

@bothzoli
May I ask how you created this file?

[bothzoli]

Sure thing, you can find all info here.
There's a tool in the VS developer console called sn.exe that can create signing key pairs.
I just ran sn.exe -k libc.eventbus.snk and took that file.

[bothzoli]

I was thinking about setting up a GitHub workflow action that would do build validation before merging a PR.
What do you think about that?
I may be able to put together something in the coming days.

[bothzoli]

Okay, I created the workflow as well, you can take a look here. Hopefully you'll have access, but posting a screenshot here in any case:

It would also be possible to add a corresponding workflow badge to the README.md (this one is now linked to my repo):

I think the workflow should automatically be called for subsequent PRs, but I'm not 100% sure TBH.

Let me know what you think 😊