Re-name Trace Section Tables

What does this MR do?

It was proposed that we re-name ci_build_trace_sections and ci_build_trace_section_names before dropping them to mitigate the risks of dependencies coming from outside the application. !66674 (comment 642597223)

Eventually, we will drop the re-named tables: !66674 (closed)

Database

▶ rake db:migrate:down VERSION=20210809194250
== 20210809194250 RenameTablesCiBuildTraceSection: reverting ==================
-- rename_table(:dep_ci_build_trace_section_names, :ci_build_trace_section_names)
   -> 0.0115s
-- rename_table(:dep_ci_build_trace_sections, :ci_build_trace_sections)
   -> 0.0057s
== 20210809194250 RenameTablesCiBuildTraceSection: reverted (0.0198s) =========

▶ rake db:migrate:up VERSION=20210809194250
== 20210809194250 RenameTablesCiBuildTraceSection: migrating ==================
-- rename_table(:ci_build_trace_sections, :dep_ci_build_trace_sections)
   -> 0.0113s
-- rename_table(:ci_build_trace_section_names, :dep_ci_build_trace_section_names)
   -> 0.0054s
== 20210809194250 RenameTablesCiBuildTraceSection: migrated (0.0168s) =========

Does this MR meet the acceptance criteria?

Conformity

• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.

Related to #337209 (closed)