fix(date-range): projected input focus restore on consecutive close

[damyanpetev]

Related to #14918

The caching of the active projected input is done on focus:

igniteui-angular/projects/igniteui-angular/src/lib/date-range-picker/date-range-picker.component.ts

Lines 1011 to 1016 in 715c43a

	private cacheFocusedInput(): void {
	if (this.hasProjectedInputs) {
	this.projectedInputs.forEach(i => {
	fromEvent(i.dateTimeEditor.nativeElement, 'focus')
	.pipe(takeUntil(this._destroy$))
	.subscribe(() => this._focusedInput = i);

Which means this handling on close:

igniteui-angular/projects/igniteui-angular/src/lib/date-range-picker/date-range-picker.component.ts

Lines 763 to 766 in 715c43a

	if (this.hasProjectedInputs && this._focusedInput) {
	this._focusedInput.setFocus();
	this._focusedInput = null;
	}

Returns the focus to the input (it's cached) and then immediately deletes it, meaning the next open won't have this and won't restore the focus back on close.

The caching should be done on open IMO, but short of refactoring that just moving the cleanup on the actual component-level blur handler.

Additional information (check all that apply):

• Bug fix
• New functionality
• Documentation
• Demos
• CI/CD

Checklist:

• All relevant tags have been applied to this PR
• This PR includes unit tests covering all the new code (test guidelines)
• This PR includes API docs for newly added methods/properties (api docs guidelines)
• This PR includes feature/README.MD updates for the feature docs
• This PR includes general feature table updates in the root README.MD
• This PR includes CHANGELOG.MD updates for newly added functionality
• This PR contains breaking changes
• This PR includes ng update migrations for the breaking changes (migrations guidelines)
• This PR includes behavioral changes and the feature specification has been updated with them