refactor(behavior_path_planner): remove maximum drivable area visualization

[zulfaqar-azmi-t4]

Description

Remove maximum drivable area visualization as it is not used anymore

#5825

Tests performed

Not applicable.

Effects on system behavior

Not applicable.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (cc1d483) 15.29% compared to head (2a59b69) 15.27%.
Report is 11 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5963      +/-   ##
==========================================
- Coverage   15.29%   15.27%   -0.02%     
==========================================
  Files        1750     1750              
  Lines      120566   120504      -62     
  Branches    36783    36739      -44     
==========================================
- Hits        18437    18411      -26     
+ Misses      81464    81460       -4     
+ Partials    20665    20633      -32     

Flag	Coverage Δ		*Carryforward flag
differential	11.69% <ø> (?)
total	15.27% <ø> (-0.02%)	⬇️	Carriedforward from cc1d483

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tfnh621]

Hi, does anyone know why this was removed or why?
I was reading the documentation on the design of the driveable area and noticed that the markers were not existing and found this PR.

autoware.universe/planning/behavior_path_planner/autoware_behavior_path_planner_common/docs/behavior_path_planner_drivable_area_design.md

Lines 166 to 178 in 2d879df

	### Visualizing maximum drivable area (Debug)
	Sometimes, the developers might get a different result between two maps that may look identical during visual inspection.
	For example, in the same area, one can perform avoidance and another cannot. This might be related to the maximum drivable area issues due to the non-compliance vector map design from the user.
	To debug the issue, the maximum drivable area boundary can be visualized.
	
	
	The maximum drivable area can be visualize by adding the marker from `/planning/scenario_planning/lane_driving/behavior_planning/behavior_path_planner/maximum_drivable_area`

autoware.universe/planning/behavior_path_planner/autoware_behavior_path_planner/README.md

Line 124 in 2d879df

| ~/debug/maximum_drivable_area | `visualization_msgs::msg::MarkerArray` | Shows maximum static drivable area | `volatile` |