WT-12986 External subsystem functions wt -> wti.

[sueloverso]

No description provided.

[evergreen-ci-prod]

Test coverage is ok, please try and improve it if that's feasible.

Metric (for added/changed code)	Coverage
Line coverage	85% (1009/1191)
Branch coverage	51% (454/886)

⚠️ This PR touches methods that have an extremely high complexity score!

• In src/btree/row_modify.c the complexity of __wt_row_modify has increased by 1 to 47.
• In src/conn/conn_reconfig.c the complexity of __wti_conn_compat_config has increased by 32 to 32.
• In src/history/hs_rec.c the complexity of __wt_hs_insert_updates has increased by 3 to 70.
• In src/lsm/lsm_merge.c the complexity of __wti_lsm_merge has increased by 38 to 38.
• In src/reconcile/rec_col.c the complexity of __wti_rec_col_fix has increased by 64 to 64.
• In src/reconcile/rec_col.c the complexity of __wti_rec_col_var has increased by 76 to 76.
• In src/reconcile/rec_row.c the complexity of __wti_rec_row_leaf has increased by 43 to 43.
• In src/reconcile/rec_visibility.c the complexity of __wti_rec_upd_select has increased by 46 to 46.
• In src/rollback_to_stable/rts_btree_walk.c the complexity of __wti_rts_btree_walk_btree_apply has increased by 34 to 34.

[sueloverso]

As you can imagine this touches most of the files. It all should be a renaming. There were a few static functions that were prefixed with wt that I fixed. Some static functions I moved before their usage in their file. But most of this should be straightforward.

Do we want to move forward with this? (I put this into the ticket also, so discussion should be recorded there.)

[sueloverso]

We agreed to move forward with this so please review.

[agorrod]

lgtm (I really just skimmed, I didn't check for correctness, but I feel like a compiler does that job better than me in this case) - I think this is a big improvement, thanks for taking the time!

[pmacko86]

LGTM, although I admit that I also was mostly just skimming. I added a few (mostly) minor comments. Thank you for the very nice cleanup - this is a good improvement!

[keitharnoldsmith]

Thanks, Sue. LGTM!

Two suggestions for additional support to go with this change.

• Could you also add an item to the coding guidelines (currently living in the top-level CONTRIBUTING.rst file) to explain __wti usage.
• Do you think it is feasible to have an s_all script that checks for cross module calls to __wti methods? If so, would you create a ticket for that?

[pmacko86]

• Do you think it is feasible to have an s_all script that checks for cross module calls to __wti methods? If so, would you create a ticket for that?

Yes, this would be great! Definitely feasible, but maybe indeed better in a separate ticket (I'd be happy to do this, if you'd like to pass it off to someone else).

[sueloverso]

@pmacko86 and @keitharnoldsmith I created WT-13031 for the dist script. I also fixed CONTRIBUTING.rst.