[BUG] Type-name collision in Schema derivation

[jumale]

Tapir version: 1.8.5

Scala version: 2.13.12

Describe the bug
When a subtype has name None, the derivedEnumeration macro confuses it with built-in Option.None type and fails with this compile error:

type mismatch;
 found   : com.example.TestEnum.None.type
 required: Option[sttp.tapir.Validator.EncodeToRaw[com.example.TestEnum]]
    (which expands to)  Option[com.example.TestEnum => Option[Any]]
  implicit lazy val schema: Schema[TestEnum] = Schema.derivedEnumeration[TestEnum].defaultStringBased

How to reproduce?

package com.example

import sttp.tapir.Schema

sealed abstract class TestEnum(val value: String) {
  override def toString: String = value
}

object TestEnum {
  case object Foo  extends TestEnum("foo")
  case object Bar  extends TestEnum("bar")
  case object None extends TestEnum("none")

  implicit lazy val schema: Schema[TestEnum] = Schema.derivedEnumeration[TestEnum].defaultStringBased
}

Additional information
A PlayJson macro for the same type manages to correctly handle this case, so I guess it should be possible to do the same in Tapir.
Also I'm not sure if it's only problem of derivedEnumeration or other macros are also affected