PHP - Traits Or Inheritance For Reducing Duplicated Code?

SELECT
    clients.CLIENT_ID, clients.CLIENT_NAME,
    orders.o_id, orders.client_id, orders.o_date, orders.o_number, orders.o_notes,
    products.o_id, products.qty, products.name
    FROM clients, orders, products
    WHERE clients.CLIENT_ID = orders.client_id
    AND orders.o_id = products.o_id
    AND orders.o_id = $theOrder

while ($row = $result->fetch_assoc()) {

    echo "<h2>$row[CLIENT_NAME]</h2>";
    echo '<label>Date</label><input type="text" value="'.timechange($row['o_date']).'" readonly><br>';
    echo '<label>Order No.</label><input type="text" value="'.$row['o_number'].'" readonly><br>';
    echo '<label>Notes</label><input type="text" value="'.$row['o_notes'].'" readonly>';
    echo '<label>Product Qty.</label><input type="text" value="'.$row['qty'].'" readonly><br>';
    echo '<label>Product Name</label><input type="text" value="'.$row['name'].'" readonly><br>';
}

I am assuming doing the following is bad practice as the short name "Account" is both for the repository and account.  Agree?  Appears that use always takes precedent over namespace and just Account\User is always short for \NotionCommotion\Domain\Entity\Account\User and not \NotionCommotion\Api\Account\User.  Still sees like it could easily result in confusion.

namespace NotionCommotion\Domain\Repository\Account;
use NotionCommotion\Domain\Entity\Account;
class AccountRepository
{
    public function getUser(string $mainKey, int $userId):?Account\User {
        //
    }
}

Would it be better to do something like the following?  Interestingly, it worked fine on the below class but when I tried to do so on the above AccountRepository class, it resulted in AccountDir\User class not found error.  Is there any logic reason why that might/should happen, or is it more likely I just have some error elsewhere?

namespace NotionCommotion\Api\Account;
use NotionCommotion\Domain\Entity\Account as AccountDir;
class AccountService
{
    public function read():AccountDir\Account {
        //
    }
}

                    <div class="blog_container">
                        <a href="/blog" class="title_link">Latest Blog Posts</a>
                        <?
                        if ($posts)
                        {
                            ?>
                            <ul>
                                <?
                                foreach ($posts as $post)
                                {
                                    ?>
                                    <li>
                                        <a href="<?= $post->guid ?>">
                                            <?= word_limiter($post->post_title, 10) ?>
                                            <span><?= date('d-m-Y', strtotime($post->post_date)) ?></span>
                                            <strong>read more ></strong>
                                        </a>
                                    </li>
                                    <?
                                }
                                ?>
                            </ul>
                            <?
                        }
                        ?>
                    </div>

class MyProductClass
{
    function computeProductA()
    {
        doSometing();
    }

    function computeProductB()
    {
        doSometingElse();
        $this->computeProductCommon();
    }

    function computeProductC()
    {
        $this->computeProductCommon();
    }

    function computeProductCommon()
    {
    }
}

Context.

Class AbstractTenantEntity's purpose is to restrict access to data to the tenant (i.e. account, owner, etc) that owns the data.  Any entity which extends it will have the TenantId added when created and the TenantId in the WHERE clause for all other requests.

Tenant typically does not have collections of the various entities which extend AbstractTenantEntity, but does for a few of them do.  When using annotation, I handled it by applying Doctrine's AssociationOverride annotation to the extended classes which should have a collection in Tenant.

use Doctrine\ORM\Mapping as ORM;

/**
 * @ORM\Entity()
 */
class Tenant
{
    /**
     * @ORM\OneToMany(targetEntity=Asset::class, mappedBy="tenant")
     */
    private $assets;

    // Other properties and typical getters and setters
}

use Doctrine\ORM\Mapping as ORM;

abstract class AbstractTenantEntity implements TenantInterface
{
    /**
     * inversedBy performed in child where required
     * @ORM\ManyToOne(targetEntity=Tenant::class)
     * @ORM\JoinColumn(nullable=false)
     */
    protected ?Tenant $tenant = null;

    // Typical getters and setters
}

use Doctrine\ORM\Mapping as ORM;

/**
 * @ORM\Entity()
 * @ORM\AssociationOverrides({
 *     @ORM\AssociationOverride(name="tenant", inversedBy="assets")
 * })
 */
class Asset extends PublicIdTenantEntity
{
    // Various properties and typical getters and setters
}

So, now I am changing from annotations to attributes, and modified AbstractTenantEntity as follows:

use Doctrine\ORM\Mapping\ManyToOne;
use Doctrine\ORM\Mapping\JoinColumn;

abstract class AbstractTenantEntity implements TenantInterface
{
    /**
     * inversedBy performed in child where required
     */
    #[ManyToOne(targetEntity: Tenant::class)]
    #[JoinColumn(nullable: false)]
    protected ?Tenant $tenant = null;

    // Typical getters and setters
}

Next I went to modify Asset and realized that there didn't appear to be an attribute for AssociationOverride.  I found a little discussion on the topic on github but couldn't find any resolution.

Question

Can inheritance be used with PHP 8 attributes where the property is defined in the parent class and the attribute is applied in the child class?  Googling php 8 attributes inheritance didn't provide anything and thus I expect the answer is no but thought I'd ask.

Thanks

EDIT.  Maybe Doctrine does have an attribute version: https://github.com/doctrine/orm/blob/2.9.x/lib/Doctrine/ORM/Mapping/AttributeOverride.php

EDIT2.  Actually don't think so