[LOGOS] Adds {Free,Open}BSD + Updates Fedora, Ubuntu & Windows

[ingrinder]

Description

• Adds logos for OpenBSD, FreeBSD
• Updates logo for Ubuntu to the new-style circle of friends inside a roundel.
• Updates Fedora logo.
• Makes lines in Windows logo look straighter.

Reason and / or context

We needed logos for the BSDs, and I thought the old Ubuntu logo was looking a bit tired. Additionally I thought the Windows & Fedora logos could do with tidying up.

How has this been tested ?

It doesn't crash when I run it with the new logos 😆

Screenshots

Fedora

I don't really know why I changed this one, we don't have to use this if you don't like it.

FreeBSD

This is the same as the FreeBSD boot-screen (as mentioned in #69)

OpenBSD

I couldn't find anything I quite liked for this... So I redrew Puffy in ASCII form. Let me know if you think it's any good 😆

Ubuntu

This is another one I redrew entirely from scratch, I didn't like the alternatives (I think the neofetch one is a bit naff)

Windows

This is just some tidying up of the edges of the windows in the flag.

Types of changes :

• Bug fix (non-breaking change which fixes an issue)
• Typo / style fix (non-breaking change which improves readability)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist :

• [IF NEEDED] I have updated the README.md file accordingly ;
• [IF NEEDED] I have updated the test cases (which pass) accordingly ;
• My changes looks good ;
• I agree that my code may be modified in the future ;
• My code follows the code style of this project (PEP8).

[HorlogeSkynet]

Thanks for all of this, I took the liberty to re-add {c[0]} as logos lines' first character to keep a consistent look with "selected" text too.

For your (and maybe others) information, I'm currently discussing with @danyspin97 how its project liveunix/liveunix-data could provide a common and consistent way to re-use distributions meta-information across "fetch-like" projects.
Of course Archey should (and surely will) use them in the future, but we are looking forward to a "more-general-purposes" specification.