fix(module:rangePicker): ShowTime issues addressed

[anddrzejb]

🤔 This is a ...

• New feature
• Bug fix
• Site / documentation update
• Demo update
• Component style update
• Bundle size optimization
• Performance optimization
• Refactoring
• Code style optimization
• Test Case
• Branch merge
• Other (about what?)

🔗 Related issue link

1. Fixes RangePicker 右侧日期选择有很多问题 #1482
   Fixes RangePicker: when ShowTime is enabled, for the second picker, the month grows by 1 when clicking any button #1680
2. Fixes RangePicker: not revert to valid value after input an invalid value in the first textbox #1677
3. Fixes RangePicker: Clicking "Ok" button doesn't transfer the cursor to the second textbox #1678
4. Focus issues
5. Visual issue for 2nd picker - extra space:
   

💡 Background and solution

1. When next month/year was clicked, base year/month (that would be incremented) was taken from the second picker instead of the first, but applied to the first. Solution applied: for the second picker, the value is decreased by predefined value to achieve expected increments.
2. After my changes, this is no longer recreatable. Either this PR fixed this or was fixed in previous PRs but not mentioned.
3. Ok click was only closing. Added logic to move to next/previous input.
4. Addresses focus remaining after selection has been made. There are still a number of issues with focus indication. I have not addressed them here as they are extremely hard to test, due to overlay issues and DatePicker spawning myriad of refresh events. Hopefully these will be easier to solve once at least overlay issues are solved (should at least be possible to write automated tests).
5. Special scenario for 2nd picker when ShowTime is true - the first picker was rendered as empty div and was causing this extra space. Removed rendering of the first picker div when 2nd is visible.

📝 Changelog

Language	Changelog
🇺🇸 English
🇨🇳 Chinese

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Changelog is provided or not needed

[github-actions]

[codecov]

Codecov Report

Merging #1788 (b963364) into master (29a723b) will increase coverage by 23.51%.
The diff coverage is 14.28%.

❗ Current head b963364 differs from pull request most recent head 297e1df. Consider uploading reports for the commit 297e1df to get more accurate results

@@             Coverage Diff             @@
##           master    #1788       +/-   ##
===========================================
+ Coverage    0.00%   23.51%   +23.51%     
===========================================
  Files         478      495       +17     
  Lines       31072    23187     -7885     
  Branches        0      121      +121     
===========================================
+ Hits            0     5452     +5452     
+ Misses      31072    17732    -13340     
- Partials        0        3        +3     

Impacted Files	Coverage Δ
components/date-picker/RangePicker.razor	0.00% <ø> (ø)
components/date-picker/RangePicker.razor.cs	0.00% <0.00%> (ø)
components/date-picker/internal/DatePickerBase.cs	46.74% <0.00%> (+46.74%)	⬆️
...nts/date-picker/internal/DatePickerDatePanel.razor	70.58% <ø> (+70.58%)	⬆️
...date-picker/internal/DatePickerDatetimePanel.razor	0.00% <0.00%> (ø)
...e-picker/internal/DatePickerDatetimePanel.razor.cs	0.00% <0.00%> (ø)
...s/date-picker/internal/DatePickerDecadePanel.razor	0.00% <ø> (ø)
...ts/date-picker/internal/DatePickerMonthPanel.razor	0.00% <ø> (ø)
.../date-picker/internal/DatePickerQuarterPanel.razor	0.00% <ø> (ø)
...nts/date-picker/internal/DatePickerYearPanel.razor	0.00% <ø> (ø)
... and 449 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 29a723b...297e1df. Read the comment docs.

[anranruye]

1. RangePicker: not revert to valid value after input an invalid value in the first textbox #1677 still exists. To reproduce this issue, you should press "enter" after input.
   

2. In react antD, the cursor is moved to the prev/next input after clicking "Ok" only one time, then the dropdown is closed. The logic of this PR is different. The cursor is moved to the prev/next input every time "Ok" is clicked unless the picker value is changed(after the picker value is changed, the cursor will still move one time, then the dropdown will be closed).
   
   

3. Focus remaining still happens when not select both date values and the picker wrongly loses focus when switch to the prev/next input(exsiting issue). In the second gif, the week range picker can not lose focus, not sure the condition to reproduce.

[anddrzejb]

1. That is really awkward 😄 . I tested this on 3 different browsers on my machine and everywhere I could not recreate it. And I was trying with Enter key... I will have another look.
2. It is not a part of this PR. Otherwise I would include the issue where you mention it. My primary goal was to solve the major issue that was making RangePicker with ShowTime unusable. Other issues - will be addressed in future PRs.
3. So... ok here? I am aware about this issue. Focus issues here gave me a headache and always consume too much of my time. I want to address them only once testing is solved, so I can actually do a fast red-green path.

[anranruye]

1. That's strange, I will also have a look.
2. Yes, this doesn't matter. I didn't mean we should have the same behavior as react ant design at this moment. But I think it's better to have a consistent behavior. Either to always move the cursor, or always close the dropdown. It's ok to make it in the future.
3. Eventually I think these issues are not parts of this PR.

[anranruye]

@anddrzejb confirmed that #1677 only happens on blazor wasm, blazor server is ok.

[anddrzejb]

I really was sure I checked wasm. I will have a look once I am avaliable.

[anddrzejb]

I found out what was it. I didn't get it on mine originally, due to the fact that for ant development, I created my own playground project where I usually work on a single component. The issue here is showing only when there are more components and jsinterop is competing with blazor. The problem here is that input value was not yet passed to DatePickerInput and already OnKeyDown event was triggered that was actually checking that value (and clearing it if it was incorrect). I do not know how else to solve this problem, except by using await Task.Delay() method, so this is how I solved it. This solution also fixed a different bug in server side - when incorrect value was entered, the input was cleared but focus was being moved to the next input. Now it stays on the same input - same as react antD.