Define DrawAreaTaskFragment in XML instead of creating programmatically

[anandwana001]

Fixes #2749

@shobhitagarwal1612 @gino-m PTAL?

[anandwana001]

This PR is a suggested approach, as the bug is no repro.

@sufyanAbbasi any suggestions?

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 61.22%. Comparing base (20d1540) to head (7c48958).

Files with missing lines	Patch %	Lines
...tacollection/tasks/polygon/DrawAreaTaskFragment.kt	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #2877      +/-   ##
============================================
+ Coverage     61.20%   61.22%   +0.01%     
  Complexity     1185     1185              
============================================
  Files           267      267              
  Lines          6400     6403       +3     
  Branches        914      914              
============================================
+ Hits           3917     3920       +3     
  Misses         1944     1944              
  Partials        539      539              

Files with missing lines	Coverage Δ
...tacollection/tasks/polygon/DrawAreaTaskFragment.kt	61.40% <83.33%> (+2.14%)	⬆️

[gino-m]

Why do we need an XML layout for an empty Fragment, especially if the rest of the Fragment is built dynamically?

Also, please include more content in the PR title, eg "Define DrawAreaTaskFragment in XML instead of creating programmatically"

[anandwana001]

Why do we need an XML layout for an empty Fragment, especially if the rest of the Fragment is built dynamically?

As of the error is coming to this particular fragment where we are dynamically generating the view using prime number, so this is one approach where rather than dependent on newly built view, we have our own XML view to use every time which will prevent this error to occur.