[FIX] report_aeroo: avoid display_name write when rendering records

[fw-bot-adhoc]

Problem

report_aeroo renders every ${...} expression through __filter. For recordset values it called _compute_display_name() directly:

return val._compute_display_name()

Calling the compute method outside the ORM compute protocol makes the record.display_name = ... assignment take Field.__set__'s business-logic branch (odoo/fields.py), which issues a real write() on the rendered model instead of only updating the cache.

Consequences:

• Printing an aeroo report as a user without write access on the rendered model raises AccessError. This surfaced when a non-admin printed a report that renders a res.country record (e.g. ${o.partner_id.country_id}) — res.country is writable only by the Settings group. It only reproduced when the report was rendered as the acting user (e.g. IoT printing via render_and_send), not through channels that render elevated.
• The method returns None, so the record was rendered empty.

Regression introduced in fa94921 (migration of name_get()[0][1] → _compute_display_name()).

Fix

Read display_name (computed into cache, no write), restoring the original name_get()[0][1] semantics:

return val[:1].display_name

How to verify

Render an aeroo report that outputs a record (e.g. ${o.partner_id.country_id}) as a user without write access on that model (non-admin, no Settings group). Before: AccessError on res.country and the value rendered empty. After: renders the display name, no write.

Ref: https://www.adhoc.inc/odoo/helpdesk.ticket/122297

Forward-Port-Of: #96

[roboadhoc]

[fw-bot-adhoc]

@mav-adhoc @maq-adhoc cherrypicking of pull request #96 failed.

stdout:

Auto-merging report_aeroo/__manifest__.py
CONFLICT (content): Merge conflict in report_aeroo/__manifest__.py
Auto-merging report_aeroo/report_parser.py

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

you can use git-fw to re-do the forward-port for you locally.

⚠️ after resolving this conflict, you will need to merge it via @roboadhoc.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[fw-bot-adhoc]

@mav-adhoc @maq-adhoc this forward port of #96 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@mav-adhoc @maq-adhoc this forward port of #96 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@mav-adhoc @maq-adhoc this forward port of #96 is awaiting action (not merged or closed).

[fw-bot-adhoc]

@mav-adhoc @maq-adhoc this forward port of #96 is awaiting action (not merged or closed).

[jcadhoc]

@roboadhoc r+ nobump