Add NG8023 extended diagnostic to report duplicate component selectors
during compilation.

This replaces the former NG0300 runtime error, ensuring the failure
occurs at build time instead of runtime.

Closes #48377

What is the current behavior?

@Component({
 selector: '[stroked-button]',
 templateUrl: './stroked-button.html',
})
export class StrokedBtn {}

@Component({
 selector: '[raised-button]',
 templateUrl: './raised-button.html',
})
export class RaisedBtn {}

@Component({
 selector: 'app-root',
 template: `
   <!-- This node has 2 selectors: stroked-button and raised-button, and both match a different component: StrokedBtnComponent, and RaisedBtnComponent , so NG0300 will be raised  -->
   <button stroked-button raised-button></button>
 `,
})
export class App {}

This only throws an error at runtime.

What is the new behavior?

Now at compile time we will get something like the following error

 NG8023: Multiple components match node with tagname button: 'StrokedBtn', 'RaisedBtn'. [plugin angular-compiler]

    src/app/app.ts:115:5:
      115 │     <button stroked-button raised-button></button>

Other information

Could we perhaps consider this a breaking change, since the error will now always be thrown, given that it only ran in development mode when it was NG0300?