return ls(@env) if @datanames not specified

[gogonzo]

teal.data::datanames() should return ls(@env) if is not specified. IMO datanames<- function shouldn't be supported and determining module's datanames should be done through module$datanames only. teal.data::datanames has been created only for teal-app to limit datanames. For teal.data package it doesn't have any usage at all and should be deprecated in the future. I think that we should use ls(get_env(<teal_data>)) instead in teal.

[github-actions]

Code Coverage Summary

Filename                         Stmts    Miss  Cover    Missing
-----------------------------  -------  ------  -------  --------------------
R/cdisc_data.R                       1       0  100.00%
R/deprecated.R                      57      57  0.00%    19-344
R/dummy_function.R                   2       2  0.00%    14-15
R/formatters_var_labels.R           61       0  100.00%
R/join_key.R                        38       0  100.00%
R/join_keys-c.R                     12       0  100.00%
R/join_keys-extract.R              128       0  100.00%
R/join_keys-names.R                 15       0  100.00%
R/join_keys-parents.R               30       0  100.00%
R/join_keys-print.R                 45       0  100.00%
R/join_keys-utils.R                 73       3  95.89%   35-38
R/join_keys.R                       21       0  100.00%
R/teal_data-class.R                 25       1  96.00%   69
R/teal_data-datanames.R             29       0  100.00%
R/teal_data-get_code.R              14       0  100.00%
R/teal_data-show.R                   4       4  0.00%    14-19
R/teal_data.R                       30      16  46.67%   33, 36-42, 52-58, 61
R/testhat-helpers.R                 26       0  100.00%
R/topological_sort.R                32       0  100.00%
R/utils-get_code_dependency.R      187       1  99.47%   282
R/verify.R                          42      11  73.81%   65, 95-99, 102-106
TOTAL                              872      95  89.11%

Diff against main

Filename                   Stmts    Miss  Cover
-----------------------  -------  ------  --------
R/join_keys.R                 -1       0  +100.00%
R/teal_data-class.R           -1       0  -0.15%
R/teal_data-datanames.R       +9       0  +100.00%
TOTAL                         +7       0  +0.09%

Results for commit: efcd0d1

Minimum allowed coverage is 80%

♻️ This comment has been updated with latest results

[github-actions]

Unit Tests Summary

  1 files   14 suites   2s ⏱️
204 tests 202 ✅ 2 💤 0 ❌
277 runs  275 ✅ 2 💤 0 ❌

Results for commit efcd0d1.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Performance Difference

Additional test case details

Test Suite	$Status$	Time on main	$±Time$	Test Case
datanames	👶		$+0.00$	datanames_returns_all_object_names_from_env_if_datasets_not_specified

Results for commit ab31046

♻️ This comment has been updated with latest results.

[m7pr]

I was wondering the other day what is the actual point of teal_data@datanames if we focus on managing module datanames with a parameter or extra set_datanames function. I am leaning toward the removal of this field and function for sure. ls(get_env(<teal_data>)) could have a useful wrapper ls_env(teal_data) in teal or in teal_data

[gogonzo]

Not needed