Accessible name Computation should not use table content

### Product

axe-core

### Product Version

4.4.3

### Latest Version

- [X] I have tested the issue with the latest version of the product

### Issue Description

#### Expectation
Describe what you expected the product to do.
For elements whose accessible names can be derived from the title attribute, and also from the contents of such elements, per the [ARIA documentation](https://www.w3.org/TR/accname-1.2/#mapping_additional_nd_te), their accessible name should be derived from the title, if they have any, before computing their name from their contents.

#### Actual
Describe what the product actually does.
For the accessible name computation of elements that can accept names from both author-provided attributes and contents, the accessible name returned by axe core is derived from the contents of such elements. This issue only happens when an element has the title attribute. However, per the [ARIA documentation](https://www.w3.org/TR/accname-1.2/#mapping_additional_nd_te) on computing accessible names, the accessible name of such elements should be derived from the title attributes rather than the contents. In other words, it seems the order of computation of accessible names does not follow the order from the [ARIA documentation](https://www.w3.org/TR/accname-1.2/#mapping_additional_nd_te).
#### How to Reproduce
Provide a code sample or link to a webpage that reproduces the issue. Without this, your issue may be closed without investigation.
```

Accessible names

Day
Miles


Friday
30

```
#### Additional context
Any thing else we should know about the issue?