ICE when Yul sub-object name with a dot shadows the name of a nested object

## Description
Sub-object names in Yul can contain dots. Dots are also used for accessing nested objects. If you try to do both at the same time so that the qualified name of a nested object matches another name that uses a dot, the compiler crashes with an ICE.

## Steps to Reproduce
### `test.yul`
```yul
object "A" {
code {}

object "B" {
code {}

object "C" {
code {}
}
}

object "B.C" {
code {}
}
}
```

### Output
```bash
solc --strict-assembly test.yul
```
```
Uncaught exception:
/solidity/libyul/Object.cpp(99): Throw in function std::set solidity::yul::Object::qualifiedDataNames() const
Dynamic exception type: boost::wrapexcept
std::exception::what: Yul assertion failed
[solidity::util::tag_comment*] = Yul assertion failed
```

Note that there is no crash if you move the definition `B.C` above `B`.

## Environment
- Compiler version: 0.8.17

Reproduce the crash with the provided test.yul and solc --strict-assembly, then inspect solidity/libyul/Object.cpp around line 99, where the assertion is reported. Compare the failing B.C and nested B.C name cases, including their definition order. Done means the compiler handles the reproducer without an ICE and the regression is covered by the project's existing test approach.

Written by the indexing model from the issue text.