snapshot method renamed to takeSnapshot

[petrknap]

• This pull request does not contain any breaking change.
• I asked the AI to briefly summarize, use and improve the feature(s), and I'm okay with the output:

Is better to keep shorter method name snapshot or expand it to something like takeSnapshot and why?

takeSnapshot offers more clarity on the method’s action, making it explicit that a snapshot is being taken. This can improve readability, especially for those new to the codebase. snapshot, while shorter, might require additional context to understand fully.

Clarity often trumps brevity in code, don’t you think? 🚀 Got more naming dilemmas or want to dive into another topic?

Could you briefly summarize the following code for me?

interface ProfilerInterface
{
    /**
     * @template TOutput of mixed
     *
     * @param callable(self): TOutput $callable
     *
     * @return ProcessableProfileInterface<TOutput> & ProfileWithOutputInterface<TOutput>
     */
    public function profile(callable $callable): ProcessableProfileInterface & ProfileWithOutputInterface;

    /**
     * @throws Exception\ProfilerCouldNotTakeSnapshotOutsideParentProfile
     */
    public function takeSnapshot(): void;
}

This interface ProfilerInterface has two methods:

1. profile(callable $callable): ProcessableProfileInterface & ProfileWithOutputInterface:
   • This method profiles the execution of a given callable.
   • It uses a template to ensure the callable can return any type of output.
   • It returns an object that implements both ProcessableProfileInterface and ProfileWithOutputInterface.
2. takeSnapshot():
   • This method takes a snapshot during profiling.
   • If called outside of a valid profiling session, it throws the ProfilerCouldNotTakeSnapshotOutsideParentProfile exception.

All set for a run-through, or want to explore another corner of this? 🚀

[petrknap]

This si implementation of hint from #13