If other applications do not see photos, there is a problem differently than you can view a package containing a photo database. Any application that needs access to you, does it through API and not through Finder. Even Finder uses a selection of photos to navigate Apple storage.
The App des deposit is not to save photos in a way optimized for file browsing. If people can see these photos, they tend to move them and break them as the application works, so the internal storage is hidden behind several layers of protection and confusion.
Apple actively discourages us from seeing internal photo storage. If you have already gained access to the photographs from Finder directly, make a backup Mac or Photo Library and then fix the library. The repair could also be tested if photos from other applications do not behave.
If it is important to look at your photos in the file system organized in folders using an album or other logical grouping, do not use photos.App.
If this is an opportunity, use something like a photo mechanic if you regularly need access to a search engine or export photos to FRASS.
Apple -related database for speed and zobpuscates file names with algorithmically generated unique file names. The database monitors more versions of each photo; Thumbnails representing several scanned versions of static photography, reduced size (space optimization is the way we set up us) version of the original full -size photo and sometimes does not even store the file locally, if stored in the cloud and space for local storage, the original and modified version of each photo is stored in the library package.