Tracking issue for rename from "object safe" to "dyn compatible"

[traviscross]

This is a tracking issue for the change to call traits that are compatible with dyn from "object safe" to "dyn compatible".

About tracking issues

Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

• Decide to do this.
  • Meeting proposal: rename "object safety" to "dyn compatibility" lang-team#286
• Update rustdoc.
  • Reword trait-object compatibility in rustdoc #126554
  • rustdoc: Rename "object safe" to "dyn compatible" #131594
  • rustdoc-JSON: Rename "object safe" to "dyn compatible" #131595
  • rustdoc: Finalize dyn compatibility renaming #135858
  • rustdoc-json-types: Finalize dyn compatibility renaming #135898
• Update the compiler.
  • Compiler: Rename "object safe" to "dyn compatible" #130826
  • Compiler & its UI tests: Rename remaining occurrences of "object safe" to "dyn compatible"  #131475
  • Refactor dyn-compatibility error and suggestions #133372
  • Compiler: Finalize dyn compatibility renaming #135860
  • Update compiler/rustc_codegen_cranelift (out of tree, not in-tree) (NOTE: only mentioned in two tests)
  • Update compiler/rustc_codegen_gcc (out of tree, not in-tree) (NOTE: only mentioned in two tests)
• Update the standard library.
  • Library: Rename "object safe" to "dyn compatible" #130827
  • Library: Finalize dyn compatibility renaming #135856
• Update the Reference.
  • Reword "object safety" as "dyn compatibility" reference#1512
  • Rename "object safe" to "dyn compatible" reference#1666
• Update the dev guide.
  • Rename "object safe" to "dyn compatible" rustc-dev-guide#2083
• Update rust-analyzer.
  • Rename object_safety rust-analyzer#18205
• Update Miri. (NOTE: only mentioned in one test)
• Update the Book.
  • Ch. 18: use “dyn compatibility” instead of “object safety” book#4129
• Update all open issues on this issue tracker (title, description).
• Fix all FIXME(dyn_compat_renaming) (mostly concerns URLs to the Reference).
• Add an entry to the relnotes (RELEASES.md).
  To do so, consider opening a new relnotes tracking issue with the relevant details.

cc @rust-lang/lang @fmease

[fmease]

I'll close this as completed. Three of the four unaddressed bullet points concern 7 tests in total (belonging to Miri / codegen_{gcc,cranelift}) and I can't be bothered to update them.

Postmortem: I failed to add this change to the release notes which is super unfortunate. Part of the reason was the fact that a beta bump occurred in the middle of updating the world (it was quite a lot). I could've maybe nominated some renames for a backport back then which I didn't do. Later, we agreed not to add it to the relnotes of 1.83 and I missed to add it to the ones of 1.84.

---

If anyone is curious, throughout the migration I used the following regex: obj(ect)?[ _-]?(un)?safe(ty)?.