``require`` can be optimized but ``assert`` cannot

## Description

For the following contract, the IR optimizer failed to optimize ``assert(i < 10)``.
```solidity
pragma solidity ^0.8.0;

contract RandomContract {
function loop() public pure {
for (uint256 i = 0; i < 10; i++) {
assert(i < 10); //failed to optimize
}
}
}
```
But if we use require, then it can be optimized.
```solidity
pragma solidity ^0.8.0;

contract RandomContract {
function loop() public pure {
for (uint256 i = 0; i < 10; i++) {
require(i < 10); //optimized
}
}
}
```

## Environment

- Compiler version: 0.8.19
- Framework/IDE (e.g. Truffle or Remix): Remix

```json
{
"language": "Solidity",
"settings": {
"viaIR": true,
"optimizer": {
"enabled": true,
"runs": 200
},
"outputSelection": {
"*": {
"": ["ast"],
"*": ["abi", "metadata", "devdoc", "userdoc", "storageLayout", "evm.legacyAssembly", "evm.bytecode", "evm.deployedBytecode", "evm.methodIdentifiers", "evm.gasEstimates", "evm.assembly"]
}
}
}
}
```

Reproduce both Solidity contracts with compiler version 0.8.19, viaIR enabled, and the optimizer configured for 200 runs, then compare their generated output. Start by tracing the IR optimizer handling for assert and require; done means assert(i < 10) is optimized in the loop as require(i < 10) is.

Written by the indexing model from the issue text.