The name `Option` is too broad

[JayBazuzi]

See design guidelines: https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces

❌ DO NOT introduce generic type names such as Element, Node, Log, and Message.

There is a very high probability that doing so will lead to type name conflicts in common scenarios. You should qualify the generic type names (FormElement, XmlNode, EventLog, SoapMessage).

There are plenty of cases besides command-line parsing where the notion of an "Option" is relevant.

[JayBazuzi]

For example, it will clash with https://github.com/louthy/language-ext/blob/e0f7edede15843b350560301e6b8cbe6b7d493fe/LanguageExt.Core/Monads/Alternative%20Monads/Option/Option.Monad.cs#L6