[Core][Actors] Duplicate named actor exception should not be lazy if possible

[glindstr]

What happened + What you expected to happen

Ray enforces the uniqueness of named actors within a namespace which is a great feature. I ran into an unexpected issue where an exception for creating a duplicate named actor doesn't present itself until the duplicate actor is interacted with. Is it feasible to make the exception thrown when creating a duplicate named remote actor?

Versions / Dependencies

Ray 2.10.0

Reproduction script

import ray
import time

@ray.remote
class TestActor:       
    def do_work(self):
        time.sleep(5)


ray.init(address="...")

name = "test"
namespace = 'namespace'

actor1 = TestActor.options(name=name, namespace=namespace, lifetime='detached').remote()
actor2 = TestActor.options(name=name, namespace=namespace, lifetime='detached').remote()

time.sleep(10)

actor1.do_work.remote()
actor2.do_work.remote() #Exception: Actor name already taken

Issue Severity

Low: It annoys or frustrates me.

[glindstr]

I see now that ray.actor.ActorClass.options has "get_if_exists" parameter which makes this potential bug a non-issue:

actor1 = TestActor.options(name=name, namespace=namespace, lifetime='detached', get_if_exists=True).remote()

Ideally this parameter is added to the api documentation:

https://docs.ray.io/en/latest/ray-core/api/doc/ray.actor.ActorClass.options.html#ray.actor.ActorClass.options