[gdal_rasterize] Also accept doubles for -ts

[elpaso]

But warn if it has a decimal part.

Fixes #11829

[jratike80]

Out of curiosity, what will be the output size when the input is -ts 100.4 200.6?

[elpaso]

Out of curiosity, what will be the output size when the input is -ts 100.4 200.6?

The same as -ts 100 200 internally casted to int (but you'll get a warning the precision was lost).

[jratike80]

If the price of one beer is 8.2€ but you have only 8, would you ask the bartender
"Is it OK if the conversion to int looses precision for the price parameter"?

How about "Warning: The value of the -ts parameter gets truncated into [lower] integer"?

[coveralls]

coverage: 70.055% (-0.008%) from 70.063%
when pulling 5be98e8 on elpaso:bugfix-gh_11829-gdal_rasterize-be-good-accept-double
into 6332083 on OSGeo:master.

[rouault]

cherry-picked to 3.10 per bb9523f

[rouault]

The backport to release/3.10 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 5be98e8ece... [gdal_rasterize] Also accept doubles for -ts
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

stdout

Auto-merging apps/gdal_rasterize_lib.cpp
CONFLICT (content): Merge conflict in apps/gdal_rasterize_lib.cpp
Auto-merging autotest/utilities/test_gdal_rasterize.py
CONFLICT (content): Merge conflict in autotest/utilities/test_gdal_rasterize.py

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release/3.10 release/3.10
# Navigate to the new working tree
cd .worktrees/backport-release/3.10
# Create a new branch
git switch --create backport-11830-to-release/3.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 5be98e8ece4e78381865056b714b889dab0a0d46,a8257444747bce33ace816c8a21e0da04b95f5dd,687fb22c024a35d474df9596e709070409a7111a
# Push it to GitHub
git push --set-upstream origin backport-11830-to-release/3.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release/3.10

Then, create a pull request where the base branch is release/3.10 and the compare/head branch is backport-11830-to-release/3.10.