[5.7] Bug fix related to extra calls to resolving callbacks (The first way)

[imanghafoori1]

Add missing tests for the resolving callbacks on the container

• bug fix related to multiple calls to resolving callbacks
  The issue is described here :
  resolving() events on interfaces are called twice  #23699
  Also a retry for:
  [5.7] Track abstracts being resolved, fire resolving events once #23701
  [5.6] Fix double firing of resolving callback #23290

[imanghafoori1]

Why a new property ?

protected $boundToClassName = [];
Since the container $app->bind(interface::class, some::class); immediately wraps string concretes like (some::class) in a closure and normalizes them in the bind method. we can not detect which one is which down the road.
So, with the help of a new protected property on the container class we keep track of them.
And we can decide later what to do.

[imanghafoori1]

Note : tests proof that the exact same problem exists for afterResolving and global callbacks too,
By placing the check around the $this->fireResolvingCallbacks($abstract, $object); we target all of them.

[imanghafoori1]

A lot of tests are added, I know they may look more than needed, but each of them cover a unique case and they all should exists.
And happy new year. 🎄 🎄

Fixed

[imanghafoori1]

Note that an other way of fixing it is made here: #27061

which I think #27066 is a lot better, this way is somewhat hacky but seems to be fully backward compatible👎