Update Limitations in README

[moritzdietz]

Update the supported platforms to include RHEL8 as well. Support for this was added with #335 but this change didn't update the README as well.

Closes #397

[moritzdietz]

I wasn't sure how you'd like the wording / listing of supported platforms.
Let me know if this should be different in case there are preferences otherwise.

[ekohl]

How about we refer users to operatingsystem_support in metadata.json for the exact OS support?

[moritzdietz]

Pro: one less thing to update whenever the supported OSes change (but how often does that really happen)
Cons: another click and another resource for the user to check.

Having it in the README has the upside that one can see right away what's what.
IMO I'd leave it there but obviously it's up to you.

[ekohl]

Pro: one less thing to update whenever the supported OSes change (but how often does that really happen)

This is what I'm mostly after. As you can see, it doesn't happen enough that we tend to mess it up. Especially since not all modules have it in their README. However, our CI relies on metadata.json so that's guaranteed to be correct. So it would be my preference to refer users there.

[moritzdietz]

I've just pushed another commit with an updated text.

[ekohl]

I'm not sure how well links render on the forge but I'm ok with it.

[ekohl]

Thanks!

[moritzdietz]

Ah I would've squashed those but thanks for doing it.
Huh yes i haven't thought about the forge so valid point.
Just thought I'd somehow link it.

[evgeni]

Doesn't the forge display the metadata anyways?

[moritzdietz]

Doesn't the forge display the metadata anyways?

Yes, it renders the contents of the metadata so that it's visible there which platform to use.
But if folks browse the GitHub repository it won't be any help there. Having the readme either specify it directly or at least link to info regarding this helps all users wherever they look at the source code. But that's just IMHO.