Ng-zorro-antd: Rename nzTitle based on the directive

[Supamiu]

What problem does this feature solve?

Having nz-tooltip, nz-popconfirm and nz-popover on the same component makes some behaviors impossible because both of them use the same input for the title: nzTitle.

This means that if you want to create a button that has a tooltip and a popover on click, you won't be able to show a tooltip at all.

What does the proposed API look like?

Use nzPopoverTitle, nzPopConfirmTitle and nzTooltipTitle as optional second input, with an implicit setter in order to map these to the effective input value and minimize the impact of this change while providing a way to solve this issue.

I'm not sure these are the only directives that should be modified, but they are the ones I spotted so far.

[wenqi73]

Ref #3448

[Supamiu]

@wenqi73 I edited the issue to add popconfirm to it, might be worth one more label :)

[avin-kavish]

This behaviour can already by achieved. I think renaming directives is a breaking change and should not be done especially when it is already working. Check this StackBlitz for a working example
```

Button

[wendellhu95]

@Supamiu you can use @avin-kavish 's code as a temporary solution. We are trying to make the the directive's name an input to make the code more readable and fix this issue.

[hsuanxyz]

https://github.com/angular/components/blob/master/src/material/tooltip/tooltip.ts#L171

@Input('nzPopconfirmTitle') nzTitle;
@Input('nzPopoverTitle') nzTitle;
@Input('nzTooltipTitle') nzTitle;

[HalfLegend]

Furthermore, the property of nzTitle is not needed at all.
We can use nzTooltip = XXX directly and this would be more concise.
Please remove the property nzTitle or mark nzTitle as not preferred

[HalfLegend]

What am I really concerned about is the properties of nzContent, nzPlacement, etc.
They all come from a directive instead of the element itself.
The name of the properties should indicate the source even if there is no conflict.

This would make the code using "ng-zorro-antd" more readable.
For example:

<button nz-popover="Popover" nzContent="Content">

At the first glance at code, I might be confused about the nzConent property. The first opinion comes to my mind might be "What is the nzContent of a button? Is it a somewhat special content of the button or some particular usage of the button content?" I wonder.
I need to further read the code more clearly and understand the nz-popover more carefully. Finally I find out the answer that the nzContent is _simply_ the content of the popover... .
I take time to understand it, but it is just, simply, only a content of a popover..... What caused my confusion is only the naming..I don't know what to say.

Furthermore, if I want to remove the nz-popover property, I may forget to remove the nzContent property together, because they have no connection, no relationship, no correlation at all from their names.

[wendellhu95]

:tada: