coredump: fix issue that nvic region overlapped by board memory region

[XuNeo]

Note: Please adhere to Contributing Guidelines.

Summary

Firstly call arm_coredump_add_region in up_initialize to add nvic region, then call coredump_set_memory_region to add board mem region, at this moment, an overlap occurs.

Impact

API coredump_set_memory_region has been removed, memory region is initialized with CONFIG_BOARD_MEMORY_RANGE.

Testing

Tested with CONFIG_ARM_COREDUMP_REGION.

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not fully meet the NuttX requirements. While it provides a summary and mentions testing, it lacks crucial details.

Missing Information:

• Insufficient Summary: The summary explains the problem but doesn't clearly state the solution. How is the overlap being resolved? Just removing coredump_set_memory_region isn't enough explanation. How are memory regions managed now?
• Incomplete Impact Assessment: The Impact section is severely lacking. It only addresses one aspect (API removal). All other impact categories (user, build, hardware, documentation, security, compatibility) are unaddressed. Even for the API removal, there's no mention of whether users will need to adapt (which they likely will).
• Vague Testing Description: "Tested with CONFIG_ARM_COREDUMP_REGION" is inadequate. What architecture, board, and configuration were used? What were the results of the tests? The required "Testing logs before change" and "Testing logs after change" sections are completely empty. There's no evidence provided that the changes actually work.
• No Issue Reference: There's no mention of a related NuttX issue, even though the template specifically requests it.

To meet the requirements, the PR needs to:

• Clarify the Solution: Explain how the memory region initialization is handled after the API removal.
• Complete the Impact Assessment: Address all impact categories. Explain the consequences of the API removal for users.
• Provide Detailed Testing Information: Specify the exact test setup (host and target details) and include actual testing logs (output) from both before and after the change, demonstrating the fix.
• Reference a Related Issue (if applicable): If this PR addresses a reported issue, link to it.

Without these improvements, the PR is incomplete and difficult to review.