[IMP] rental: change to physical service product

[meval1006]

What this PR does and why it's needed

Reworks the Rental app's service products documentation to distinguish between physical service products (e.g., hotel rooms, work stations) and non-physical (labor) service products, which now require different configuration steps. The rewrite adds a full walkthrough for setting up a physical service product synced with the Planning app, using a running hotel-room example throughout.

Changes

Service products (Rental)

• Retitled service_products.rst to "Physical service rental products" and reframed the intro to explain that physical and labor (non-physical) services require different configurations
• Added a new "Configure materials and a role for the physical product" section explaining how to set up a Planning role and materials so shifts sync with the physical product, illustrated with a hotel example (Shady Grove Deluxe Room)
• Updated "Create a new service product" to require the Sales and Planning apps, set the Invoicing Policy to Prepaid/Fixed Price, and configure the product's Role page with the Sync Shifts and Rental Orders checkbox
• Updated the base rental period/price section with descriptions for the Pickup and Return fields, in addition to Periodicity and Padding Time
• Added a new "Set up variants" section showing how to configure product attributes (e.g., bed type, occupancy) for a physical service product
• Simplified the pricelist creation guidance and clarified that the Prices tab requires the Pricelists feature to be enabled
• Added a tip on adding a Validity date range column to pricelist rules
• Added a new "eCommerce features" section describing how the eCommerce tab configures the product's website page
• Added six new screenshots illustrating the Planning role/materials setup, the physical service product form, the Role page, and product variants

Rental product types

• Added a rental/product_type/configuration anchor to product_type.rst so the Configuration section can be cross-referenced from the service products page

Rental orders

• Updated create_rental_order.rst to note that smart-button app integration depends on the service product type, replacing the reference to the removed "properly configured" anchor

---

This saas-19.3 PR should not be FWP.

[robodoo]

[meval1006]

Hi @jero-odoo, this PR is ready to review. I am testing out the Skill.md file to summarize the PR.

[jero-odoo]

Nice work @meval1006 ! Just a few notes

[meval1006]

Hi @erjer-odoo, this review is ready for final review.

[erjer-odoo]

Sorry there are so many comments; there were just some issues that I noticed while reviewing the file. As soon as you fix them, though, it should be good to go.

@robodoo delegate+

[meval1006]

@robodoo FW=no

[robodoo]

@meval1006 unknown command 'FW'.

For your own safety I've ignored everything in your entire comment.

Currently available commands:

command
help	displays this help
r(eview)+	approves the PR, if it's a forwardport also approves all non-detached parents
r(eview)=<number>	only approves the specified parents
r(eview)-	removes approval of a previously approved PR, if the PR is staged the staging will be cancelled
retry	re-tries staging a PR in the "error" state
fw=no	does not forward-port this PR
fw=default	forward-ports this PR normally
fw=skipci	does not wait for a forward-port's statuses to succeed before creating the next one
fw=skipmerge	does not wait for the source to be merged before creating forward ports
up to <branch>	only ports this PR forward to the specified branch (included)
merge	integrate the PR with a simple merge commit, using the PR description as message
rebase-merge	rebases the PR on top of the target branch the integrates with a merge commit, using the PR description as message
rebase-ff	rebases the PR on top of the target branch, then fast-forwards
squash	squashes the PR as a single commit on the target branch, using the PR description as message
delegate+	grants approval rights to the PR author
delegate=<...>	grants approval rights on this PR to the specified github users
check	fetches or refreshes PR metadata, resets mergebot state
remindme:<branch>=<message>	When the PR gets forward-ported to <branch>, ping you with <message>. <message> can be quoted if it needs spaces.

Note: this help text is dynamic and will change with the state of the PR.

[meval1006]

@robodoo fw=no

[robodoo]

Disabled forward-porting.

[meval1006]

@robodoo r+